Searched hist:1.344 (Results 1 - 25 of 79) sorted by relevance
| /src/doc/ | ||
| H A D | BRANCHES | 1.344 Wed Nov 08 20:24:53 GMT 2017 matt branches: 1.344.2; Add matt-nb8-mediatek branch 1.344 Wed Nov 08 20:24:53 GMT 2017 matt branches: 1.344.2; Add matt-nb8-mediatek branch |
| /src/ | ||
| H A D | build.sh | 1.344 Mon Sep 14 09:02:11 GMT 2020 kim Fix typo in usage |
| H A D | UPDATING | 1.344 Sun Sep 24 16:33:41 GMT 2023 gutteridge UPDATING: fix a couple of spelling mistakes |
| /src/sys/arch/macppc/conf/ | ||
| H A D | GENERIC | 1.344 Mon Feb 26 23:09:32 GMT 2018 sevan branches: 1.344.2; Remove support for macofcons(4), it's not actually possible to build a kernel with it enabled - See PR port-macppc/53004 and it may have further problems even so. From <macallan>: "There is some early console code that uses OF output but it causes problems when we get close to MMU setup - I think it can go, it hasn't been enabled in any config in at least a decade as far as I know." 1.344 Mon Feb 26 23:09:32 GMT 2018 sevan branches: 1.344.2; Remove support for macofcons(4), it's not actually possible to build a kernel with it enabled - See PR port-macppc/53004 and it may have further problems even so. From <macallan>: "There is some early console code that uses OF output but it causes problems when we get close to MMU setup - I think it can go, it hasn't been enabled in any config in at least a decade as far as I know." |
| /src/sys/kern/ | ||
| H A D | init_sysent.c | 1.344 Thu Oct 03 16:51:34 GMT 2024 christos regen |
| H A D | vfs_subr.c | 1.344 Tue May 06 18:43:44 GMT 2008 ad branches: 1.344.2; PR kern/38141 lookup/vfs_busy acquire rwlock recursively Simplify the mount locking. Remove all the crud to deal with recursion on the mount lock, and crud to deal with unmount as another weirdo lock. Hopefully this will once and for all fix the deadlocks with this. With this commit there are two locks on each mount: - krwlock_t mnt_unmounting. This is used to prevent unmount across critical sections like getnewvnode(). It's only ever read locked with rw_tryenter(), and is only ever write locked in dounmount(). A write hold can't be taken on this lock if the current LWP could hold a vnode lock. - kmutex_t mnt_updating. This is taken by threads updating the mount, for example when going r/o -> r/w, and is only present to serialize updates. In order to take this lock, a read hold must first be taken on mnt_unmounting, and the two need to be held across the operation. One effect of this change: previously if an unmount failed, we would make a half hearted attempt to back out of it gracefully, but that was unlikely to work in a lot of cases. Now while an unmount that will be aborted is in progress, new file operations within the mount will fail instead of being delayed. That is unlikely to be a problem though, because if the admin requests unmount of a file system then s(he) has made a decision to deny access to the resource. 1.344 Tue May 06 18:43:44 GMT 2008 ad branches: 1.344.2; PR kern/38141 lookup/vfs_busy acquire rwlock recursively Simplify the mount locking. Remove all the crud to deal with recursion on the mount lock, and crud to deal with unmount as another weirdo lock. Hopefully this will once and for all fix the deadlocks with this. With this commit there are two locks on each mount: - krwlock_t mnt_unmounting. This is used to prevent unmount across critical sections like getnewvnode(). It's only ever read locked with rw_tryenter(), and is only ever write locked in dounmount(). A write hold can't be taken on this lock if the current LWP could hold a vnode lock. - kmutex_t mnt_updating. This is taken by threads updating the mount, for example when going r/o -> r/w, and is only present to serialize updates. In order to take this lock, a read hold must first be taken on mnt_unmounting, and the two need to be held across the operation. One effect of this change: previously if an unmount failed, we would make a half hearted attempt to back out of it gracefully, but that was unlikely to work in a lot of cases. Now while an unmount that will be aborted is in progress, new file operations within the mount will fail instead of being delayed. That is unlikely to be a problem though, because if the admin requests unmount of a file system then s(he) has made a decision to deny access to the resource. |
| H A D | kern_sig.c | 1.344 Wed May 16 00:42:15 GMT 2018 kamil Correct handling of: vfork(2) + PT_TRACE_ME + raise(2) Follow the FreeBSD approach of not routing signals to the parent that is a became tracer after calling PT_TRACE_ME by the vfork(2)ed child (before exec(3)/exit(3)). Now if a child calls raise(3), the signal is processed directly to this child. Add new ATF ptrace(2) tests: - traceme_vfork_raise1 (SIGKILL) - traceme_vfork_raise2 (SIGSTOP) // temporarily disabled - traceme_vfork_raise3 (SIGABRT) - traceme_vfork_raise4 (SIGHUP) - traceme_vfork_raise5 (SIGCONT) The FreeBSD implementation introduces P_PPTRACE for this special case. Right know keep opencoding check of this case in the kernel. It might be refactored in future. The Linux kernel does not follow this approach and causes dead locking of the processes (parent and child). Defer handling SIGSTOP into future. This is an intermediate step towards correct handling of fork(2) and vfork(2) in the context of ptrace(2). All new tests pass. There are no regressions in existing ATF ptrace(2) tests. Sponsored by <The NetBSD Foundation> |
| H A D | kern_synch.c | 1.344 Sat Mar 14 20:23:51 GMT 2020 ad Make page waits (WANTED vs BUSY) interlocked by pg->interlock. Gets RW locks out of the equation for sleep/wakeup, and allows observing+waiting for busy pages when holding only a read lock. Proposed on tech-kern. |
| /src/sys/arch/alpha/alpha/ | ||
| H A D | machdep.c | 1.344 Mon Mar 24 20:06:31 GMT 2014 christos branches: 1.344.2; use cpu_{g,s}etmodel 1.344 Mon Mar 24 20:06:31 GMT 2014 christos branches: 1.344.2; use cpu_{g,s}etmodel |
| /src/sys/arch/amd64/amd64/ | ||
| H A D | machdep.c | 1.344 Fri Dec 13 20:14:25 GMT 2019 ad branches: 1.344.2; Break the global uvm_pageqlock into a per-page identity lock and a private lock for use of the pagedaemon policy code. Discussed on tech-kern. PR kern/54209: NetBSD 8 large memory performance extremely low PR kern/54210: NetBSD-8 processes presumably not exiting PR kern/54727: writing a large file causes unreasonable system behaviour 1.344 Fri Dec 13 20:14:25 GMT 2019 ad branches: 1.344.2; Break the global uvm_pageqlock into a per-page identity lock and a private lock for use of the pagedaemon policy code. Discussed on tech-kern. PR kern/54209: NetBSD 8 large memory performance extremely low PR kern/54210: NetBSD-8 processes presumably not exiting PR kern/54727: writing a large file causes unreasonable system behaviour |
| /src/distrib/sets/lists/debug/ | ||
| H A D | mi | 1.344 Sat Dec 12 03:03:14 GMT 2020 pgoyette branches: 1.344.2; Also add the new test to the sets lists. 1.344 Sat Dec 12 03:03:14 GMT 2020 pgoyette branches: 1.344.2; Also add the new test to the sets lists. |
| H A D | shl.mi | 1.344 Mon Jul 08 22:35:09 GMT 2024 christos bump libssh, add sshd-session |
| /src/sys/rump/librump/rumpkern/ | ||
| H A D | rump.c | 1.344 Mon Mar 23 14:49:50 GMT 2020 pgoyette branches: 1.344.2; Don't attempt to detach an evcnt before attaching it. If its not already attached, we will panic. It turns out that this check wasn't really needed anyway, it was simply paranoia on my part. Thanks to hannken@ for bringing this to my attention. 1.344 Mon Mar 23 14:49:50 GMT 2020 pgoyette branches: 1.344.2; Don't attempt to detach an evcnt before attaching it. If its not already attached, we will panic. It turns out that this check wasn't really needed anyway, it was simply paranoia on my part. Thanks to hannken@ for bringing this to my attention. |
| /src/sys/sys/ | ||
| H A D | proc.h | 1.344 Tue Jan 09 20:55:43 GMT 2018 maya branches: 1.344.2; remove struct emul's e_fault. It used to be used by COMPAT_IRIX for the purpose of overriding uvm_fault (only implemented in MIPS), now removed. Ride 8.99.12 version bump. 1.344 Tue Jan 09 20:55:43 GMT 2018 maya branches: 1.344.2; remove struct emul's e_fault. It used to be used by COMPAT_IRIX for the purpose of overriding uvm_fault (only implemented in MIPS), now removed. Ride 8.99.12 version bump. |
| /src/sys/arch/alpha/conf/ | ||
| H A D | GENERIC | 1.344 Sat Mar 10 21:51:48 GMT 2012 joerg P1003_1B_SEMAPHORE is no longer optional. |
| /src/distrib/sets/lists/comp/ | ||
| H A D | shl.mi | 1.344 Tue Sep 29 18:33:22 GMT 2020 roy rumpify vether(4) |
| /src/share/misc/ | ||
| H A D | acronyms.comp | 1.344 Wed Mar 01 15:45:00 GMT 2023 fcambus Add RTTI (run-time type information). |
| /src/share/mk/ | ||
| H A D | bsd.prog.mk | 1.344 Wed May 24 10:07:16 GMT 2023 lukem deprecate SHAREDSTRINGS build option Hasn't worked for at least 20 years (and never in the cross-build environment, nor did it work with parallel make), and has never been needed in NetBSD as we don't have the older BSD programs (pascal, pre-nvi ex) that needed mkstr/xstr on PDP-11. PR toolchain/35964 |
| /src/sys/dev/scsipi/ | ||
| H A D | sd.c | 1.344 Sat Apr 12 10:25:26 GMT 2025 mlelstv Use WRITE_16 for dumps when necessary. |
| /src/sys/ufs/ffs/ | ||
| H A D | ffs_vfsops.c | 1.344 Fri Feb 17 08:29:11 GMT 2017 hannken Untangle VFS_SYNC() from VFS_SUSPENDCTL(). |
| /src/sys/ufs/lfs/ | ||
| H A D | lfs_vfsops.c | 1.344 Tue Sep 01 06:11:06 GMT 2015 dholland Make the inode fields in the 64-bit superblock 64 bits wide. Reasoning as before. Note that I am not going through and checking for 64->32 truncations in inode numbers; I'm sure there are quite a few, but that's a project for later. |
| H A D | lfs_vnops.c | 1.344 Wed Oct 01 14:16:11 GMT 2025 perseant Align case labels with 8-character tab stops. No functional change. |
| /src/sys/uvm/ | ||
| H A D | uvm_map.c | 1.344 Sat May 06 21:34:52 GMT 2017 joerg Extend the mmap(2) interface to allow requesting protections for later use with mprotect(2), but without enabling them immediately. Extend the mremap(2) interface to allow duplicating mappings, i.e. create a second range of virtual addresses references the same physical pages. Duplicated mappings can have different effective protections. Adjust PAX mprotect logic to disallow effective protections of W&X, but allow one mapping W and another X protections. This obsoletes using temporary files for purposes like JIT. Adjust PAX logic for mmap(2) and mprotect(2) to fail if W&X is requested and not silently drop the X protection. Improve test cases to ensure correct operation of the changed interfaces. |
| /src/sys/arch/sparc64/sparc64/ | ||
| H A D | locore.s | 1.344 Sat Nov 10 01:35:14 GMT 2012 nakayama Use macro instead of magic number. |
| /src/sys/dev/ata/ | ||
| H A D | wd.c | 1.344 Wed Sep 05 05:36:19 GMT 2007 jnemeth yet more caddr_t fallout |
Completed in 448 milliseconds