Source-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[src/netbsd-7-0]: src/doc tickets 996-999
details: https://anonhg.NetBSD.org/src/rev/15235207d0fc
branches: netbsd-7-0
changeset: 801063:15235207d0fc
user: snj <snj%NetBSD.org@localhost>
date: Thu Nov 05 09:35:43 2015 +0000
description:
tickets 996-999
diffstat:
doc/CHANGES-7.0.1 | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 66 insertions(+), 1 deletions(-)
diffs (78 lines):
diff -r bfd9e2c3d5b9 -r 15235207d0fc doc/CHANGES-7.0.1
--- a/doc/CHANGES-7.0.1 Thu Nov 05 09:35:23 2015 +0000
+++ b/doc/CHANGES-7.0.1 Thu Nov 05 09:35:43 2015 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: CHANGES-7.0.1,v 1.1.2.4 2015/11/04 18:21:20 riz Exp $
+# $NetBSD: CHANGES-7.0.1,v 1.1.2.5 2015/11/05 09:35:43 snj Exp $
A complete list of changes from the NetBSD 7.0 release to the NetBSD 7.0.1
release:
@@ -27,3 +27,68 @@
Fix incorrect argument of mii_anar(). Fixes PR#50206.
[msaitoh, ticket #971]
+sys/kern/kern_exec.c 1.419, 1.420
+sys/kern/kern_exit.c 1.246, 1.247
+sys/kern/kern_synch.c 1.309
+
+ In execve_runproc(), update the p_waited entry for the process
+ being moved to SSTOP state, not for its parent. If the value is
+ not already zero, it could prevent its parent from waiting for
+ the process. Fixes PR kern/50298
+ --
+ When clearing out the scheduler queues during system shutdown,
+ we move all processes to the SSTOP state. Make sure we update
+ each process's p_waited and the parents' p_nstopchild counters
+ to maintain consistent values. Fixes PR kern/50318
+ --
+ Currently, if a process is exiting and its parent has indicated
+ no intent of reaping the process (nor any other children), the
+ process will get reparented to init. Since the state of the
+ exiting process at this point is SDEAD, proc_reparent() will not
+ update either the old or new parent's p_nstopchild counters.
+ This change causes both old and new parents to be properly
+ updated. Fixes PR kern/50300
+ --
+ For processes marked with PS_STOPEXIT, update the process's
+ p_waited value, and update its parent's p_nstopchild value when
+ marking the process's p_stat to SSTOP. The process needed to be
+ SACTIVE to get here, so this transition represents an additional
+ process for which the parent needs to wait. Fixes PR kern/50308
+ --
+ In spawn_return() we temporarily move the process state to SSTOP,
+ but without updating its p_waited value or its parent's
+ p_nstopchild counter. Later, we restore the original state,
+ again without any adjustment of the related values. This leaves
+ a relatively short window when the values are inconsistent and
+ could interfere with the proper operation of sys_wait() for the
+ parent. If during this window, any of the checks being made
+ result in an error, we call exit1() which will eventually migrate
+ the process's state to SDEAD (with an intermediate transition to
+ SDYING). At this point the other variables get updated, and we
+ finally restore a consistent state.
+ This change updates the p_waited and parent's p_nstopchild at each
+ step to eliminate any windows during which the values could lead
+ to incorrect decisions. Fixes PR kern/50330
+ [pgoyette, ticket #996]
+
+sys/kern/kern_sig.c 1.321
+
+ When delivering a signal, it's possible that the process's state
+ in p_stat is SACTIVE yet p_sflag is PS_STOPPING (while waiting
+ for other LWPs to stop). In that case, we don't want to adjust
+ the parent's p_nstopchild count.
+ [pgoyette, ticket #997]
+
+sys/compat/linux/arch/arm/linux_ptrace.c 1.19
+sys/compat/linux/arch/i386/linux_ptrace.c 1.31
+sys/compat/linux/arch/powerpc/linux_ptrace.c 1.29
+
+ Don't release proc_lock until we're done looking at things that
+ are protected by the lock, particularly p_stat and p_waited.
+ [pgoyette, ticket #998]
+
+sys/kern/kern_exit.c 1.248
+
+ Update value of p_stat before we release the proc_lock.
+ [pgoyette, ticket #999]
+
Home |
Main Index |
Thread Index |
Old Index