OpenBSD src changes summary for 2016-03-27 ==========================================
bin/ed distrib/armv7 etc/netstart lib/libc lib/libssl sys/dev sys/dev/ic sys/dev/sdmmc sys/isofs/cd9660 sys/isofs/udf sys/kern sys/miscfs/fuse sys/msdosfs sys/netinet sys/ntfs sys/ufs/ext2fs sys/ufs/ffs sys/uvm usr.bin/calendar usr.bin/dc usr.sbin/ntpd usr.sbin/rcctl == bin =============================================================== 01/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/bin ed ~ ed.h > actually remove unnecessary includes > from Edgar Pettijohn, ok and with input from tb@ (mmcc@) == distrib =========================================================== 02/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib armv7 ~ miniroot/Makefile.inc ~ ramdisk/install.md > use MLO not mlo to match the names generated by u-boot builds (jsg@) ~ miniroot/Makefile.inc ~ ramdisk/install.md > Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i. > The offset of u-boot.img in the disk image changes to be the same as > wandboard. (jsg@) == etc =============================================================== 03/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc netstart ~ netstart > Don't delete the 224/4 route in netstart, unless it's being done to ensure > that > a -reject route can be added. Restores the ability to set an interface > route > before daemons are started, lost during the previous simplification. > ok millert mpi (sthen@) == lib =============================================================== 04/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib libc ~ sys/execve.2 > Add EISDIR to ERRORS and fix ETXTBSY description; from Piotr Durlej. > OK jmc@ (millert@) ~ gen/syslog_r.c > remove unused variable > ok millert@ (chl@) ~ arch/sparc/sys/syscall.S > Switch to RSYSCALL: no special handling is needed here any more and > we do need the hidden _libc_syscall alias. > from miod@ (guenther@) ~ arch/mips64/sys/syscall.S > Don't need to define SYS_sycall here > noted by miod@ (guenther@) libssl ~ src/ssl/s3_clnt.c > Merge a memleak fix from BoringSSL 6b6e0b2: > https://boringssl.googlesource.com/boringssl/+/6b6e0b20893e2be0e68af605a60f > fa2cbb0ffa64%5E!/#F0 > ok millert@, beck@ (mmcc@) == sys =============================================================== 05/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys dev ~ ipmi.c > Always sleep at same priority. > ok uebayasi@ (mpi@) dev/ic ~ aac.c > Kill async code commented out for more than 10 years. (mpi@) dev/sdmmc ~ sdhc.c ~ sdhcvar.h > Make it possible to override the standard card detect mechanism. The SD > controller on Intel's Bay Trail SoC tends to be used in a way where a > separate gpio is used that signals the presence of a card in a slot. This > change allows us to support that mode. > ok stsp@ (kettenis@) isofs/cd9660 ~ cd9660_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) isofs/udf ~ udf_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) kern ~ vfs_syscalls.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) miscfs/fuse ~ fuse_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) msdosfs ~ msdosfs_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) netinet ~ tcp_input.c ~ tcp_var.h > To prevent attacks on the hash buckets of the syn cache, our TCP > stack reseeds the hash function every time the cache is empty. > Unfortunatly the attacker can prevent the reseeding by sending > unanswered SYN packes periodically. > Fix this by having an active syn cache that gets new entries and a > passive one that is idling out. When the passive one is empty and > the active one has been used 100000 times, they switch roles and > the hash function is reseeded with new random. > tedu@ agrees; OK mpi@ (bluhm@) ntfs ~ ntfs_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) ufs/ext2fs ~ ext2fs_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) ufs/ffs ~ ffs_vfsops.c > When pulling and unmounting an umass USB stick, the file system > could end up in an inconsistent state. The fstype dependent > mp->mnt_data was NULL, but the general mp was still listed as a > valid mount point. Next access to the file system would crash with > a NULL pointer dereference. > If closing the device fails, the mount point must go away anyway. > There is nothing we can do about it. Remove the workaround for the > EIO error in the general unmount code, but do not generate any error > in the file system specific unmount functions. > OK natano@ beck@ (bluhm@) uvm ~ uvm_amap.c ~ uvm_amap.h ~ uvm_map.c > amap_extend is never called, remove it. > In the code, this function is called when vm_map_entries are merged. > However, only kernel map entries are merged, and these do not use amaps. > Therefore amap_extend() is never called at runtime. > ok millert@, KASSERT suggestion and ok mpi@ (stefan@) == usr.bin =========================================================== 06/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin calendar ~ calendars/calendar.music ~ calendars/de_DE.UTF-8/calendar.musik > Fix spelling of "Beverly Hills". From Carson Chittom. (tim@) dc ~ bcode.c ~ stack.c > some style(9) and redundant tests for NULL, from Michael W. Bombardieri > (otto@) == usr.sbin ========================================================== 07/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin ntpd ~ control.c ~ ntpd.h > Rename session_socket_blockmode() to session_socket_nonblockmode(), > removing its second parameter and the enum() that provided the > values for said parameter. > The function was only called with the second parameter set to one > value (BM_NONBLOCKING) from the enum(). So just do the right thing. > Similar to changes made in smtpd. > While here remove the pointless third parameter from the fcntl(F_GETFL) > call. > No functional change. > ok guenther@ bcook@ deraadt@ (krw@) rcctl ~ rcctl.sh > Make usage() a bit more user friendly wrt "action" and "lsarg". > prodded by espie@ (ajacoutot@) ~ rcctl.sh > Compute "action" from the _rc_actions variable. (ajacoutot@) =============================================================================== _______________________________________________ odc mailing list [email protected] http://www.squish.net/mailman/listinfo/odc
