Searched hist:1.302 (Results 1 - 25 of 117) sorted by relevance
| /src/tests/usr.bin/xlint/lint1/ | ||
| H A D | msg_215.c | 1.11 Sun Aug 29 17:01:27 GMT 2021 rillig lint: in C99 mode, make implicit function declarations an error In tree.c 1.294 from 2021-06-28, I had already tried this, but at that time, there were too many implicit function definitions in the NetBSD tree. Most of them were GCC builtins, which lint did not recognize. Therefore I had to revert to a warning in tree.c 1.302 from 2021-06-30. In the meantime, lint has learnt to recognize compiler builtins, see is_compiler_builtin, so try again now. The build logs from x86_64, i386, sparc and sparc64 show no more implicit function declarations. |
| /src/sys/sys/ | ||
| H A D | syscallargs.h | 1.302 Fri Aug 14 00:55:03 GMT 2020 riastradh branches: 1.302.2; regen 1.302 Fri Aug 14 00:55:03 GMT 2020 riastradh branches: 1.302.2; regen |
| H A D | syscall.h | 1.302 Tue Dec 19 18:34:47 GMT 2017 kamil Drop SYS_sbrk sbrk - change data segment size This syscall is dummy since the inception of the project. Sponsored by <The NetBSD Foundation> |
| H A D | systm.h | 1.302 Mon May 22 14:07:24 GMT 2023 riastradh uiomove(9): Add uiopeek/uioskip operations. This allows a caller to grab some data, consume part of it, and atomically update the uio with only the amount it consumed. This way, the caller can use a buffer of a size that doesn't depend on how much it will actually consume, which it may not know in advance -- e.g., because it depends on how much an underlying hardware tty device will accept before it decides it has had too much. Proposed on tech-kern: https://mail-index.netbsd.org/tech-kern/2023/05/09/msg028883.html (Opinions were divided between `uioadvance' and `uioskip'. I stuck with `uioskip' because that was less work for me.) |
| H A D | vnode.h | 1.302 Mon Jul 18 04:30:30 GMT 2022 thorpej Make kqueue event status for vnodes shareable, and for stacked file systems like nullfs, make the upper vnode share that status with the lower vnode. And, lo, NetBSD 9.99.99. Fixes PR kern/56713. |
| /src/sys/kern/ | ||
| H A D | syscalls.c | 1.302 Sun Jul 03 14:26:47 GMT 2016 christos branches: 1.302.2; regen 1.302 Sun Jul 03 14:26:47 GMT 2016 christos branches: 1.302.2; regen |
| H A D | init_sysent.c | 1.302 Mon Nov 30 22:48:53 GMT 2015 pgoyette Regen for 7.99.23 |
| H A D | kern_sig.c | 1.302 Wed Dec 30 23:31:56 GMT 2009 rmind branches: 1.302.2; sigactsunshare(): set reference count in a case of new sigacts allocation. Bug (e.g. memory leak) can happen when using clone(2) call. 1.302 Wed Dec 30 23:31:56 GMT 2009 rmind branches: 1.302.2; sigactsunshare(): set reference count in a case of new sigacts allocation. Bug (e.g. memory leak) can happen when using clone(2) call. |
| H A D | uipc_socket.c | 1.302 Sat Apr 09 23:52:22 GMT 2022 riastradh branches: 1.302.4; unix(4): Convert membar_exit to membar_release. Use atomic_load_consume or atomic_load_relaxed where necessary. Comment on why unlocked nonatomic access is valid where it is done. 1.302 Sat Apr 09 23:52:22 GMT 2022 riastradh branches: 1.302.4; unix(4): Convert membar_exit to membar_release. Use atomic_load_consume or atomic_load_relaxed where necessary. Comment on why unlocked nonatomic access is valid where it is done. |
| H A D | syscalls.master | 1.302 Wed Apr 22 21:22:21 GMT 2020 thorpej Remove _lwp_gettid(2) system call. This problem is going to be solved another way. (Note: this call was never exposed in libc, so we can just recycle the syscall number.) |
| H A D | tty.c | 1.302 Mon Oct 03 19:57:06 GMT 2022 riastradh constty(4): Make MP-safe. Access to the global constty variable is coordinated as follows: 1. Setting constty to nonnull, with atomic_store_release, is allowed only under the new adaptive constty_lock in thread context. This serializes TIOCCONS operations and ensures unlocked readers can safely use a constty pointer read with atomic_load_consume. 2. Changing constty from nonnull to null, with atomic_cas_ptr, is allowed in any context -- printf(9) uses this to disable a broken constty. 3. Reading constty under constty_lock is allowed with atomic_load_relaxed, because while constty_lock is held, it can only be made null by some other thread/CPU, never made nonnull. 4. Reading constty outside constty_lock is allowed with atomic_load_consume in a pserialize read section -- constty is only ever made nonnull with atomic_store_release, in (1). ttyclose will wait for all these pserialize read sections to complete before flushing the tty. 5. To continue to use a struct tty pointer in (4) after the pserialize read section has completed, caller must use tty_acquire during the pserialize read section and then tty_release when done. ttyclose will wait for all these references to drain before returning. These access rules allow us to serialize TIOCCONS, and safely destroy ttys, without putting any locks on the access paths like printf(9) that use constty. Once we set D_MPSAFE, operations on /dev/console will contend only with other users of the same tty as constty, which will be an improvement over contending with all other kernel lock users in the system. |
| H A D | vfs_bio.c | 1.302 Wed Mar 30 10:34:14 GMT 2022 riastradh kern: Sprinkle biglock-slippage assertions. We seem to have a poltergeist that occasionally messes with the biglock depth, but it's very hard to reproduce and only manifests as some other CPU spinning out on the kernel lock which is no good for diagnostics. |
| /src/ | ||
| H A D | build.sh | 1.302 Sun Nov 16 05:38:10 GMT 2014 uebayasi build.sh mkernel=*: New command to build kernel in modular |
| /src/sys/arch/sparc/sparc/ | ||
| H A D | machdep.c | 1.302 Mon Feb 08 19:02:31 GMT 2010 joerg branches: 1.302.2; Remove separate mb_map. The nmbclusters is computed at boot time based on the amount of physical memory and limited by NMBCLUSTERS if present. Architectures without direct mapping also limit it based on the kmem_map size, which is used as backing store. On i386 and ARM, the maximum KVA used for mbuf clusters is limited to 64MB by default. The old default limits and limits based on GATEWAY have been removed. key_registered_sb_max is hard-wired to a value derived from 2048 clusters. 1.302 Mon Feb 08 19:02:31 GMT 2010 joerg branches: 1.302.2; Remove separate mb_map. The nmbclusters is computed at boot time based on the amount of physical memory and limited by NMBCLUSTERS if present. Architectures without direct mapping also limit it based on the kmem_map size, which is used as backing store. On i386 and ARM, the maximum KVA used for mbuf clusters is limited to 64MB by default. The old default limits and limits based on GATEWAY have been removed. key_registered_sb_max is hard-wired to a value derived from 2048 clusters. |
| H A D | pmap.c | 1.302 Thu Jun 16 04:17:49 GMT 2005 briggs branches: 1.302.2; 1.302.8; Rename 'ncpus' to 'sparc_ncpus' to avoid shadow warnings in m.i. code. Also sprinkle an __UNVOLATILE() for sparc. n.b. sparc64 'cpus' should probably be renamed to 'cpu_info_list' to match i386 et al. 1.302 Thu Jun 16 04:17:49 GMT 2005 briggs branches: 1.302.2; 1.302.8; Rename 'ncpus' to 'sparc_ncpus' to avoid shadow warnings in m.i. code. Also sprinkle an __UNVOLATILE() for sparc. n.b. sparc64 'cpus' should probably be renamed to 'cpu_info_list' to match i386 et al. 1.302 Thu Jun 16 04:17:49 GMT 2005 briggs branches: 1.302.2; 1.302.8; Rename 'ncpus' to 'sparc_ncpus' to avoid shadow warnings in m.i. code. Also sprinkle an __UNVOLATILE() for sparc. n.b. sparc64 'cpus' should probably be renamed to 'cpu_info_list' to match i386 et al. |
| /src/sys/arch/amiga/conf/ | ||
| H A D | GENERIC | 1.302 Wed Jun 05 23:08:00 GMT 2013 christos branches: 1.302.2; remove obsolete networking options 1.302 Wed Jun 05 23:08:00 GMT 2013 christos branches: 1.302.2; remove obsolete networking options |
| /src/share/misc/ | ||
| H A D | acronyms | 1.302 Wed Jun 10 20:26:52 GMT 2020 sevan URM |
| /src/sys/arch/alpha/alpha/ | ||
| H A D | machdep.c | 1.302 Wed Nov 28 17:40:03 GMT 2007 ad branches: 1.302.10; 1.302.14; Hook in the atomic ops on alpha. 1.302 Wed Nov 28 17:40:03 GMT 2007 ad branches: 1.302.10; 1.302.14; Hook in the atomic ops on alpha. 1.302 Wed Nov 28 17:40:03 GMT 2007 ad branches: 1.302.10; 1.302.14; Hook in the atomic ops on alpha. |
| /src/doc/ | ||
| H A D | BRANCHES | 1.302 Fri Jan 07 01:11:03 GMT 2011 matt Note matt-nb5-pq3 branch |
| /src/sys/ufs/ffs/ | ||
| H A D | ffs_vfsops.c | 1.302 Fri Nov 14 10:09:50 GMT 2014 manu branches: 1.302.2; Fix use-after-free on failed unmount with extended attribute enabled When unmount failed, for instance because the mount is still busy, UFS1 extended attributes structures were left freed while the kernel assumes extended attributes were still enabled. This led to using UFS1 extended attributes structures after free. With LOCKDEBUG, with quickly triggers a panic. The problem is fixed by: 1) clear MNT_EXTATTR flag after extended attributes structures are freed 2) attempt to restart extended attributes after failed unmount 2) set MNT_EXTATTR correctly after extended attributes restart As a side effect, extended attribute structures are now only initialized when extended attributes are started for the filesystem. 1.302 Fri Nov 14 10:09:50 GMT 2014 manu branches: 1.302.2; Fix use-after-free on failed unmount with extended attribute enabled When unmount failed, for instance because the mount is still busy, UFS1 extended attributes structures were left freed while the kernel assumes extended attributes were still enabled. This led to using UFS1 extended attributes structures after free. With LOCKDEBUG, with quickly triggers a panic. The problem is fixed by: 1) clear MNT_EXTATTR flag after extended attributes structures are freed 2) attempt to restart extended attributes after failed unmount 2) set MNT_EXTATTR correctly after extended attributes restart As a side effect, extended attribute structures are now only initialized when extended attributes are started for the filesystem. |
| /src/sys/dev/scsipi/ | ||
| H A D | cd.c | 1.302 Sun Apr 04 21:36:22 GMT 2010 martin branches: 1.302.2; cd_size: if we fake a size (and I realy have no idea why this would be a good idea), at least set up all values to the fake values, as the caller expects. Should fix PR kern/39904, though if noone can find out why the fake value would be needed, we should change it to just return 0 as suggested in the PR. 1.302 Sun Apr 04 21:36:22 GMT 2010 martin branches: 1.302.2; cd_size: if we fake a size (and I realy have no idea why this would be a good idea), at least set up all values to the fake values, as the caller expects. Should fix PR kern/39904, though if noone can find out why the fake value would be needed, we should change it to just return 0 as suggested in the PR. |
| /src/sys/dev/pci/ | ||
| H A D | files.pci | 1.302 Sat Feb 09 00:25:43 GMT 2008 ober branches: 1.302.6; Intel PRO/Wireless LAN 4965AGN Mini-PCI Adapter Driver ported from OpenBSD by deroote@. OK nick@ moof@ 1.302 Sat Feb 09 00:25:43 GMT 2008 ober branches: 1.302.6; Intel PRO/Wireless LAN 4965AGN Mini-PCI Adapter Driver ported from OpenBSD by deroote@. OK nick@ moof@ |
| /src/usr.bin/xlint/lint1/ | ||
| H A D | decl.c | 1.302 Sat Oct 01 10:04:06 GMT 2022 rillig branches: 1.302.2; lint: miscellaneous cleanup No functional change. 1.302 Sat Oct 01 10:04:06 GMT 2022 rillig branches: 1.302.2; lint: miscellaneous cleanup No functional change. |
| /src/sys/netinet/ | ||
| H A D | ip_input.c | 1.302 Mon Jun 25 15:28:39 GMT 2012 christos branches: 1.302.2; rename rfc6056 -> portalgo, requested by yamt 1.302 Mon Jun 25 15:28:39 GMT 2012 christos branches: 1.302.2; rename rfc6056 -> portalgo, requested by yamt |
| /src/sys/arch/sparc64/sparc64/ | ||
| H A D | machdep.c | 1.302 Tue Sep 07 16:56:13 GMT 2021 riastradh Revert "ksyms: Use pserialize(9) for kernel access to ksyms." |
Completed in 405 milliseconds