Module Name: src
Committed By: snj
Date: Sat Nov 7 20:52:40 UTC 2015
Modified Files:
src/doc [netbsd-5]: CHANGES-5.3
Log Message:
tickets 1972, 1974, 1975, 1978-1981
To generate a diff of this commit:
cvs rdiff -u -r1.1.2.125 -r1.1.2.126 src/doc/CHANGES-5.3
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/doc/CHANGES-5.3
diff -u src/doc/CHANGES-5.3:1.1.2.125 src/doc/CHANGES-5.3:1.1.2.126
--- src/doc/CHANGES-5.3:1.1.2.125 Tue Sep 15 00:03:00 2015
+++ src/doc/CHANGES-5.3 Sat Nov 7 20:52:40 2015
@@ -1,4 +1,4 @@
-# $NetBSD: CHANGES-5.3,v 1.1.2.125 2015/09/15 00:03:00 riz Exp $
+# $NetBSD: CHANGES-5.3,v 1.1.2.126 2015/11/07 20:52:40 snj Exp $
A complete list of changes from the NetBSD 5.2 release to the NetBSD 5.3
release:
@@ -3990,3 +3990,91 @@ crypto/dist/openssl/util/mkerr.pl patch
POODLE fix in October last year that caused the SSL server side to
fail to handshake.
[spz, ticket#1976]
+
+lib/libm/src/lrint.c 1.5
+lib/libm/src/lrintf.c 1.6
+
+ Return x for >= DBL_FRACBITS in lrint.c.
+ Return x for >= SNG_FRACBITS in lrintf.c
+
+ Addresses PR lib/49690
+ [nat, ticket #1972]
+
+sys/ufs/lfs/lfs_segment.c 1.247 via patch
+
+ Fix catastrophic bug in lfs_rewind() that changed segment
+ numbers (lfs_curseg/lfs_nextseg in the superblock) using the
+ wrong units. These fields are for whatever reason the start
+ addresses of segments (measured in frags) rather than the
+ segment numbers 0..n. Only affects dumping from a mounted
+ file system.
+ [dholland, ticket #1974]
+
+libexec/ftpd/logwtmp.c 1.26
+libexec/ftpd/logwtmp.c 1.27
+
+ ftpd(8): Don't write uninitialized data to wtmpx files.
+ [shm, ticket #1975]
+
+sys/dev/mii/atphy.c 1.17
+
+ Fix incorrect argument of mii_anar(). Fixes PR#50206.
+ [msaitoh, ticket #1978]
+
+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 #1979]
+
+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 lwp's to stop). In that case, we don't want to adjust
+ the parent's p_nstopchild count.
+ [pgoyette, ticket #1980]
+
+sys/kern/kern_exit.c 1.248
+
+ Update value of p_stat before we release the proc_lock.
+ [pgoyette, ticket #1981]
+
