OpenBSD src changes summary for 2016-05-27 ==========================================
distrib/miniroot etc/examples/pkg.conf etc/rc lib/libc lib/libtls sbin/mount sbin/mount_ffs sbin/mount_nfs sys/arch/alpha/include sys/arch/amd64/stand/libsa sys/arch/arm/include sys/arch/i386/stand/libsa sys/arch/m88k/include sys/arch/sh/include sys/arch/sparc/include sys/arch/sparc64/include sys/kern sys/sys sys/uvm usr.bin/aucat usr.bin/ftp usr.bin/tmux usr.bin/vi usr.sbin/httpd usr.sbin/pkg_add usr.sbin/pstat == distrib =========================================================== 01/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib miniroot ~ install.sub > During install, set new 'wxallowed' mount option for the filesystem > /usr/local resides on. > idea from and ok deraadt > with feedback from halex (rpe@) ~ install.sub > whitespaces grow bsd.rd, you know (deraadt@) == etc =============================================================== 02/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc examples/pkg.conf ~ examples/pkg.conf > sync (sthen@) rc ~ rc > Add function comments. > OK sthen, deraadt (rpe@) ~ rc > No need to show the messages if we skip in case of /usr/lib on nfs. > OK deraadt (rpe@) == lib =============================================================== 03/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib libc ~ asr/asr.c > typo fixes; Anthony Coulter (sthen@) ~ sys/mmap.2 ~ sys/mount.2 ~ sys/mprotect.2 > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) libtls ~ tls_init.3 > typo fixes; Anthony Coulter (sthen@) ~ tls.h > Fix function parameters that do not have an underscore prefix. (jsing@) ~ tls_config.c > Avoid leaking ca_mem when freeing a tls_config. (jsing@) ~ tls.c ~ tls_config.c ~ tls_internal.h > Rename some of the internal error setting functions to more closely follow > existing naming standards. Also provide functions for setting a struct > tls_error * directly (rather than having to have a struct tls * or a > struct tls_config *). (jsing@) == sbin ============================================================== 04/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin mount ~ mntopts.h ~ mount.8 ~ mount.c > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) mount_ffs ~ mount_ffs.c > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) mount_nfs ~ mount_nfs.c > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) == sys =============================================================== 05/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys arch/alpha/include ~ asm.h > Remove the non ELF macros > ok millert (deraadt@) arch/amd64/stand/libsa ~ bioscons.c > Modify com_init to match the com driver initializaiton, and add > a short delay so that baud rate changes on the console have > a chance of working. Lots of help from theo on this one. > Makes my serial console on my APU work for an unattended > reboot instead of hanging when garbage is echoed to the tty. > ok deraadt@ (beck@) arch/arm/include ~ asm.h ~ profile.h > Remove the non ELF macros > ok millert (deraadt@) arch/i386/stand/libsa ~ bioscons.c > Modify com_init to match the com driver initializaiton, and add > a short delay so that baud rate changes on the console have > a chance of working. Lots of help from theo on this one. > Makes my serial console on my APU work for an unattended > reboot instead of hanging when garbage is echoed to the tty. > ok deraadt@ (beck@) arch/m88k/include ~ asm.h > Remove the non ELF macros > ok millert (deraadt@) arch/sh/include ~ asm.h ~ profile.h > Remove the non ELF macros > ok millert (deraadt@) arch/sparc/include ~ asm.h ~ profile.h > Remove the non ELF macros > ok millert (deraadt@) arch/sparc64/include ~ asm.h > Remove the non ELF macros > ok millert (deraadt@) kern ~ kern_pledge.c > rename(2) operation requires "rpath cpath" at the underlying operation > (the src path lookup is considered a rpath operation) > noticed by kristaps, discussed with semarie (deraadt@) ~ kern_sysctl.c ~ vfs_syscalls.c > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) sys ~ mount.h ~ sysctl.h > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) uvm ~ uvm_mmap.c > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) == usr.bin =========================================================== 06/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin aucat ~ aucat.c ~ dsp.c ~ dsp.h > Make resamp_do() get the exact number input and output samples and > provide routines to calculate them. This way we don't rely on it > to calculate the bytes procuded/consumed anymore. No behaviour change. > (ratchov@) ~ aucat.c > Simplify slot_fill() and slot_flush(). No behaviour change (ratchov@) ~ aucat.c > Flush rec buffer if there's less than one block space left and refill > play buffer if there's less than one block of data left. This is the > correct condition in the general case. No behaviour change, as all > input/output is multiple of the block size. (ratchov@) ~ aucat.c ~ dsp.c > When resampling, use the exact resampling factor instead of the ratio > between input and output block sizes. This was inherited from sndiod, > but is not required for files because they are continuous streams of > samples and do not need to be split in blocks of equal duration. > This change makes playback/recording rate match exactly the requested > sample rate. (ratchov@) ftp ~ fetch.c ~ main.c > Per the libtls man page, tls_init() must be called prior to any other > tls_* function; so actually do that. (jsing@) tmux ~ tmux.c ~ tmux.h > Use getprogname() instead of __progname to make portability easier. (nicm@) ~ utf8.c > Most of the utf8_data is fixed so simplify utf8_set to use a memcpy. > (nicm@) ~ screen-write.c > Break the save-last-cell code into a separate function (so it can be > called conditionally later). (nicm@) ~ screen-write.c > Padding cell is always the same so use a static. (nicm@) vi ~ cl/cl.h ~ cl/cl_funcs.c ~ cl/cl_read.c ~ cl/cl_term.c ~ common/args.h ~ common/cut.c ~ common/cut.h ~ common/exf.c ~ common/gs.h ~ common/key.c ~ common/key.h ~ common/log.c ~ common/main.c ~ common/mark.c ~ common/mark.h ~ common/put.c ~ common/screen.h ~ common/seq.c ~ common/seq.h ~ common/util.c ~ docs/interp/interp ~ ex/ex.h ~ ex/ex_abbrev.c ~ ex/ex_append.c ~ ex/ex_argv.c ~ ex/ex_at.c ~ ex/ex_cd.c ~ ex/ex_display.c ~ ex/ex_file.c ~ ex/ex_global.c ~ ex/ex_map.c ~ ex/ex_print.c ~ ex/ex_read.c ~ ex/ex_script.c ~ ex/ex_subst.c ~ ex/ex_txt.c ~ include/cl_extern.h ~ include/com_extern.h ~ include/ex_extern.h ~ include/vi_extern.h ~ vi/v_at.c ~ vi/v_ch.c ~ vi/v_put.c ~ vi/v_txt.c ~ vi/v_ulcase.c ~ vi/vi.c ~ vi/vi.h ~ vi/vs_line.c ~ vi/vs_msg.c ~ vi/vs_split.c > Revert CHAR_T removal. Some signedness flaws were introduced. > Found the hard way by jca@ (martijn@) == usr.sbin ========================================================== 07/07 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin httpd ~ server_http.c > Return "400 Bad Request" instead of "500 Server Internal Error" for > requests lacking "HTTP/<version>". > This makes it more obvious that httpd(8) does not attempt to support > HTTP v0.9 (circa 1991), when "GET <url>\r\n" was valid. > ok millert@ florian@ (krw@) pkg_add ~ fw_update.1 > tweak wording to avoid "firmware which are installed" (tj@) pstat ~ pstat.c > W^X violations are no longer permitted by default. A kernel log message > is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag > kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump > creation. > W^X violating programs can be permitted on a ffs/nfs filesystem-basis, > using the "wxallowed" mount option. One day far in the future > upstream software developers will understand that W^X violations are a > tremendously risky practice and that style of programming will be > banished outright. Until then, we recommend most users need to use the > wxallowed option on their /usr/local filesystem. At least your other > filesystems don't permit such programs. > ok jca kettenis mlarkin natano (deraadt@) =============================================================================== _______________________________________________ odc mailing list [email protected] http://www.squish.net/mailman/listinfo/odc
