OpenBSD src changes summary for 2017-05-03 ==========================================
etc/changelist etc/mtree/special lib/libc lib/libutil sbin/init sys/arch/amd64/amd64 sys/arch/amd64/include sys/arch/arm64/arm64 sys/arch/sparc64/sparc64 sys/dev sys/dev/pci sys/dev/usb sys/net sys/netinet sys/netinet6 sys/sys sys/uvm usr.bin/encrypt usr.bin/less usr.bin/lock usr.bin/skey usr.bin/ssh usr.bin/systat usr.bin/tmux usr.bin/x99token usr.sbin/dhcpd usr.sbin/syspatch usr.sbin/tokeninit usr.sbin/vmd == etc =============================================================== 01/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc changelist ~ changelist > add vm.conf to changelist and mtree/special > OK reyk mlarkin (gsoares@) mtree/special ~ mtree/special > add vm.conf to changelist and mtree/special > OK reyk mlarkin (gsoares@) == lib =============================================================== 02/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib libc ~ net/gai_strerror.3 > make the description strings match the code (deraadt@) libutil ~ imsg_init.3 > spacing (in EXAMPLES code) (reyk@) == sbin ============================================================== 03/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin init ~ init.c > Use the safe idiom of cleaning sensitive data from memory with > explicit_bzero, > instead of relying on other methods, after readpassphrase. Some programs on > this diff won't benefit that much since it happens near the terminal path, > but > someone might copy the unsafe idiom to another program and place it where > it > may leak sensitive data. > Discussed aeons ago with tb@, OK deraadt@ and beck@ (mestre@) == sys =============================================================== 04/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys arch/amd64/amd64 ~ fpu.c ~ vmm.c ~ vmm_support.S TAGGED OPENBSD_6_1 > OpenBSD 6.1 errata 002, May 2, 2017 > vmm(4) mismanaged floating point contexts. (jsg@) arch/amd64/include ~ cpufunc.h ~ fpu.h ~ vmmvar.h TAGGED OPENBSD_6_1 > OpenBSD 6.1 errata 002, May 2, 2017 > vmm(4) mismanaged floating point contexts. (jsg@) arch/arm64/arm64 ~ machdep.c > Bring boot() in line with our other architectures. > ok mpi@, deraadt@ (kettenis@) arch/sparc64/sparc64 ~ pmap.c > explicitly initialise the mutex in the kernel map. > previously it was zeroed memory from a global, which kind of looks > like a valid mutex, but we shouldnt rely on that. > ok kettenis@ (dlg@) dev ~ softraid_concat.c TAGGED OPENBSD_6_1 > OpenBSD 6.1 errata 004, May 2, 2017 > softraid(4) was unable to create usable concat volumes because > it always set the size of the volume to zero sectors. (jsg@) ~ softraid_concat.c TAGGED OPENBSD_6_0 > OpenBSD 6.0 errata 21, May 1, 2017 > softraid(4) was unable to create usable concat volumes because > it always set the size of the volume to zero sectors. (jsg@) ~ audio.c TAGGED OPENBSD_6_0 > style improvement from Michael W. Bombardieri <mb at ii.net> (ratchov@) dev/pci ~ if_ix.c TAGGED OPENBSD_6_1 > MFC > Since rev 1.1 ix has attempted to require a 64 bit BAR, the test for > this was wrong and was corrected at the end of last year in rev 1.140. > Before then a 64 bit BAR was not enforced as the test was wrong. > It turns out there exist 82598 parts which have a 32 bit BAR so change > the test to only require a memory BAR and not a 64 bit memory BAR. > Problem reported by Robert Blacquiere. ok mikeb@ (jsg@) ~ if_iwmreg.h TAGGED OPENBSD_6_1 > Fix a regression in iwm(4) which made 3165 devices unusable. > When MIMO support was added several entries in the rate table index enum > got a wrong value. On most devices the firmware ended up using a Tx rate > different from the rate net80211 asked for (which is bad, but not fatal). > But on 3165 devices which do not support MIMO the firmware rightly raised > a fatal error whenever the driver mistakenly asked for a MIMO Tx rate. > Reported by Georgios Pediaditis, Steve Throckmorton, and Kai Wirt on misc@ > Thanks to benno@ for providing 3165 hardware I could use to debug this. > (stsp@) dev/usb ~ uaudio.c > Remove unused (and wrong) uaudio_drain() call. From Michael W. > Bombardieri" <[email protected]>. (ratchov@) ~ if_umb.c > Byte order of IP addresses was broken on big endian machines. > MBIM already uses network byte order for IP addresses, so just > use them as they are. > ok stsp@, deraadt@ (gerhard@) net ~ ifq.c ~ ifq.h > add ifq_mfreem() so ifq backends can free packets during dequeue. > a goal of the ifq api is to avoid freeing an mbuf while holding a > lock. to acheive this it allowed the backend enqueue operation to > return a single mbuf to be freed. however, mikeb@ is working on a > backend that wants to free packets during dequeue. to support this, > ifq_mfreem queues a packet during dequeue for freeing at the end > of the ifq serialiser. > there's some doco in ifq.h about it. > requested by mikeb@ (dlg@) ~ ifq.h > update the stack doco to match reality. > i hadnt documented that api changes made to support multiple ifqueues > on a single ifnet. > a glaring omission is doco for if_attach_queues, but that should > go into a manpage for driver writers to read, not internal doco on > the stack. (dlg@) ~ ifq.c ~ ifq.h > Provide a function to dispose of a list of mbufs on dequeue > ifq_mfreeml() is similar to the ifq_mfreem(), but takes an mbuf list > as an argument. This also lets these functions subtract the number > of packets to be disposed of from the ifq length. > OK dlg (mikeb@) netinet ~ tcp_input.c > Back out rev 1.185 (which made the code match the comment) and > adjust the comment to match reality (or at least rfc7323) instead. > This brings us back in line with the behavior of Net and Free. > From Lauri Tirkkonen. OK bluhm@ (millert@) netinet6 ~ ip6_output.c > Change the ip6_setmoptions() function to receive the rdomain as a new > parameter. This makes the ip6_setmoptions() function look more like the > ipv4 version and fixes a problem with IPV6_JOIN_GROUP when no interface > is specified. > ok bluhm@ (rzalamena@) sys ~ mbuf.h > Provide a signed 64 bit integer timestamp in the mbuf packet header > The precision of the timestamp is not fixed yet, but there's a strong > argument to measure it in nanoseconds. > With suggestions from kettenis, dlg, miod and deraadt. > OK deraadt@, sthen@ (mikeb@) uvm ~ uvm_vnode.c > Mark uvm_sync_lock as vnode'ish for witness purposes, as it is taken > between mount locks and inode locks, which may been recorded in either > order > ok visa@ (guenther@) == usr.bin =========================================================== 05/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin encrypt ~ encrypt.c > Use the safe idiom of cleaning sensitive data from memory with > explicit_bzero, > instead of relying on other methods, after readpassphrase. Some programs on > this diff won't benefit that much since it happens near the terminal path, > but > someone might copy the unsafe idiom to another program and place it where > it > may leak sensitive data. > Discussed aeons ago with tb@, OK deraadt@ and beck@ (mestre@) less ~ tags.c > While freeing tag entries, make sure to free the copied strings. > From Anton Lindqvist. OK tobias@ nicm@ (millert@) lock ~ lock.c > Use the safe idiom of cleaning sensitive data from memory with > explicit_bzero, > instead of relying on other methods, after readpassphrase. Some programs on > this diff won't benefit that much since it happens near the terminal path, > but > someone might copy the unsafe idiom to another program and place it where > it > may leak sensitive data. > Discussed aeons ago with tb@, OK deraadt@ and beck@ (mestre@) skey ~ skey.c > Use the safe idiom of cleaning sensitive data from memory with > explicit_bzero, > instead of relying on other methods, after readpassphrase. Some programs on > this diff won't benefit that much since it happens near the terminal path, > but > someone might copy the unsafe idiom to another program and place it where > it > may leak sensitive data. > Discussed aeons ago with tb@, OK deraadt@ and beck@ (mestre@) ssh ~ sftp.1 ~ ssh-add.1 ~ ssh-keygen.1 ~ ssh.1 > more protocol 1 stuff to go; ok djm (jmc@) ~ ssh_config > more protocol 1 bits removed; ok djm (jmc@) ~ clientloop.c ~ kex.h ~ opacket.h ~ packet.c ~ packet.h ~ pathnames.h ~ ssh.h ~ ssh_config.5 ~ sshkey.h > remove miscellaneous SSH1 leftovers; ok markus@ (naddy@) ~ scp.1 ~ sftp.1 ~ ssh.1 ~ ssh_config.5 > restore mistakenly deleted description of the ConnectionAttempts option > ok markus@ (naddy@) systat ~ pftop.c > Remove unused PRIO column from the queueing display; ok sthen@ (mikeb@) tmux ~ format.c ~ status.c ~ tmux.1 ~ tmux.h ~ window-copy.c > Add a format for the last search string in copy mode and fix the prompt > so it can work when in -I, suggested by Suraj N Kurapati. (nicm@) x99token ~ x99token.c > Use the safe idiom of cleaning sensitive data from memory with > explicit_bzero, > instead of relying on other methods, after readpassphrase. Some programs on > this diff won't benefit that much since it happens near the terminal path, > but > someone might copy the unsafe idiom to another program and place it where > it > may leak sensitive data. > Discussed aeons ago with tb@, OK deraadt@ and beck@ (mestre@) == usr.sbin ========================================================== 06/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin dhcpd ~ conflex.c ~ confpars.c ~ dhcp.c ~ dhcpd.conf.5 ~ dhcpd.h ~ dhctoken.h TAGGED OPENBSD_6_1 > OpenBSD 6.1 errata 001, May 2, 2017 > dhcpd(8) unconditionally echoed client identifier. Add parameter > "echo-client-id" to allow this behaviour to be turned off. (jsg@) syspatch ~ syspatch.sh > - Don't make an empty syspatch/ repo an error; having no available patch > is perfectly legit. > - Abort immediately if we cannot reach our mirror server listed in > installurl. > - Return a proper error code when running without arguments and we cannot > list the available patches. (ajacoutot@) ~ syspatch.sh > Output explicit error messages for: > - trying to install files mounted on a remote FS (diskless clients etc.) > - read-only FS > - not enough space on FS > These were all properly catched before (syspatch would refuse to do > anything) > but the error message was a bit cryptic. (ajacoutot@) tokeninit ~ tokeninit.c > Use the safe idiom of cleaning sensitive data from memory with > explicit_bzero, > instead of relying on other methods, after readpassphrase. Some programs on > this diff won't benefit that much since it happens near the terminal path, > but > someone might copy the unsafe idiom to another program and place it where > it > may leak sensitive data. > Discussed aeons ago with tb@, OK deraadt@ and beck@ (mestre@) vmd ~ parse.y > Sort parser tokens, no functional change (reyk@) =============================================================================== _______________________________________________ odc mailing list [email protected] http://www.squish.net/mailman/listinfo/odc
