OpenBSD src changes summary for 2016-03-13
==========================================

lib/csu                                 lib/libc
lib/libssl                              regress/lib
sys/arch/amd64/amd64                    sys/arch/amd64/include
sys/dev/pci                             sys/kern
sys/net                                 usr.bin/kdump
usr.bin/vi                              usr.sbin/config
usr.sbin/vmctl                          usr.sbin/vmd

== lib =============================================================== 01/05 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib

csu

  ~ alpha/md_init.h                       ~ hppa/md_init.h
  ~ hppa64/md_init.h                      ~ mips64/md_init.h
  ~ sparc64/md_init.h                     

  > crt0.c is already setting environ, so don't set it in MD_START_SETUP
  > ok kettenis@ mpi@ (guenther@)

libc

  ~ gen/exec.c                            ~ gen/getprogname.c
  ~ gen/posix_spawn.c                     ~ gen/setproctitle.c
  ~ gen/setprogname.c                     ~ gen/syslog_r.c
  ~ gen/verr.c                            ~ gen/verrc.c
  ~ gen/verrx.c                           ~ gen/vwarn.c
  ~ gen/vwarnc.c                          ~ gen/vwarnx.c
  ~ gmon/gmon.c                           ~ hidden/stdlib.h
  ~ stdlib/getenv.c                       ~ stdlib/malloc.c
  ~ stdlib/setenv.c                       ~ stdlib/system.c
  ~ sys/stack_protector.c                 

  > environ and __progname are not declared in a public header; declare them
  > in libc's hidden/stdlib.h instead of in each .c file that needs one
  > ok deraadt@ gsoares@ mpi@ (guenther@)

libssl

  ~ src/doc/crypto/EVP_PKEY_decrypt.pod   ~ src/doc/crypto/EVP_PKEY_encrypt.pod

  > Fix examples for EVP_PKEY_CTX_set_rsa_padding.
  > Noted here, https://github.com/libressl-portable/portable/issues/161, we
  > document a non-existent constant in the examples for
  > EVP_PKEY_CTX_set_rsa_padding.
  > ok deraadt@ (bcook@)

== regress =========================================================== 02/05 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/regress

lib

  ~ libcrypto/bn/general/bntest.c         

  > check return value for BN_hex2bn in regression tests (bcook@)

== sys =============================================================== 03/05 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys

arch/amd64/amd64

  ~ vmm.c                                 

  > Introduce memory ranges to support VMs with >= 4G RAM
  > Kernel bits:
  > - When creating a VM, a list of memory ranges has to be specified,
  > similar to the BIOS memory map. This is necessary for VMs with
  > RAM sizes approaching 4G because we'll need PCI MMIO space in
  > the higher parts of the 32 bit address space.
  > vmctl and vmd bits:
  > - Construct appropriate memory ranges to create a VM with a given
  > RAM size
  > - Construct a corresponding BIOS memory map from the memory ranges
  > and update the boot params page accordingly.
  > - Make sure that all variables that represent guest physical addresses
  > match the address width of the target CPU instead of using uint32_t.
  > - Fix some integer promotion glitches that actually restricted VM
  > RAM size to 2G.
  > This changes the VM create ioctl interface, so update your kernel,
  > vmd, and vmctl.
  > ok mlarkin@ (stefan@)

arch/amd64/include

  ~ vmmvar.h                              

  > Introduce memory ranges to support VMs with >= 4G RAM
  > Kernel bits:
  > - When creating a VM, a list of memory ranges has to be specified,
  > similar to the BIOS memory map. This is necessary for VMs with
  > RAM sizes approaching 4G because we'll need PCI MMIO space in
  > the higher parts of the 32 bit address space.
  > vmctl and vmd bits:
  > - Construct appropriate memory ranges to create a VM with a given
  > RAM size
  > - Construct a corresponding BIOS memory map from the memory ranges
  > and update the boot params page accordingly.
  > - Make sure that all variables that represent guest physical addresses
  > match the address width of the target CPU instead of using uint32_t.
  > - Fix some integer promotion glitches that actually restricted VM
  > RAM size to 2G.
  > This changes the VM create ioctl interface, so update your kernel,
  > vmd, and vmctl.
  > ok mlarkin@ (stefan@)

dev/pci

  ~ ichiic.c                              

  > In ichiic(4), ignore the SMBALERT# interrupt. This interrupt has been
  > observed to fire for spurious reasons with buggy hardware/bios.
  > It is being ignored by both FreeBSD and Linux as well.
  > Fixes GENERIC kernel boot on ADI RCC-VE with buggy bios versions, where
  > ichiic(4) ended up stealing interrupts from ehci(4), rendering the internal
  > eMMC flash unusable.
  > Also, always ackknowledge all interrupts by writing status bits back
  > to avoid a potential SMBALERT# interrupt storm.
  > with and ok deraadt@ kettenis@ mpi@ (stsp@)

kern

  ~ kern_pledge.c                         

  > corrects on off-by-one error in pledge_namei()
  > - rewrite canonpath() to not require extra byte before shrinking
  > - make canonpath() error not fatal for the caller (proposition from tedu@)
  > ok millert@ tedu@ deraadt@ (semarie@)

  ~ kern_pledge.c                         

  > pledge: let wl_paths works well with chroot
  > it factorizes path resolution in resolvpath() function, and use it in
  > sys_pledge() and pledge_namei().
  > please note that wl_paths is still disabled. (semarie@)

  ~ kern_pledge.c                         

  > pledge: replace #if 0 printf with DNPRINTF macro (semarie@)

  ~ kern_pledge.c                         

  > reenable wl_paths (whitelisted-paths) in pledge(2) (semarie@)

  ~ kern_pledge.c                         

  > keep disabled wl_paths for now. the expensiveness impact need to be better
  > considered.
  > ok deraadt@ (semarie@)

net

  ~ if_vlan.c                             

  > consistencly name ifnet pointers like we did in carp
  > the vlan interface is ifp, the vlans parent interface is ifp0, the new
  > interface parent is newifp0.
  > requested by mpi@
  > no binary change (dlg@)

  ~ if_vlan.c                             

  > i forgot to rename p to ifp0 in vlan_config
  > still no binary change. (dlg@)

== usr.bin =========================================================== 04/05 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin

kdump

  ~ Makefile                              ~ mkioctls

  > Recognize ipmi, vscsi, pvbus, udl, fuse, trunk, pipex and memrange
  > ioctl requests. (natano@)

vi

  ~ vi/v_cmd.c                            

  > remove an extra space before ^\ help message.
  > Fixes allignment in viusage
  > By Raf Czlonka (martijn@)

== usr.sbin ========================================================== 05/05 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin

config

  ~ config.8                              

  > one more un-vax, which i fixed but somehow didn;t commit;
  > Xr fix while here... (jmc@)

vmctl

  ~ vmctl.c                               

  > Introduce memory ranges to support VMs with >= 4G RAM
  > Kernel bits:
  > - When creating a VM, a list of memory ranges has to be specified,
  > similar to the BIOS memory map. This is necessary for VMs with
  > RAM sizes approaching 4G because we'll need PCI MMIO space in
  > the higher parts of the 32 bit address space.
  > vmctl and vmd bits:
  > - Construct appropriate memory ranges to create a VM with a given
  > RAM size
  > - Construct a corresponding BIOS memory map from the memory ranges
  > and update the boot params page accordingly.
  > - Make sure that all variables that represent guest physical addresses
  > match the address width of the target CPU instead of using uint32_t.
  > - Fix some integer promotion glitches that actually restricted VM
  > RAM size to 2G.
  > This changes the VM create ioctl interface, so update your kernel,
  > vmd, and vmctl.
  > ok mlarkin@ (stefan@)

vmd

  ~ vmm.c                                 

  > Rework an erroneous warning message about 16 bit i8253 PIT counter I/O.
  > The unimplemented mode is MSB/LSB (8 bit), not 16 bit mode. (mlarkin@)

  ~ loadfile.h                            ~ loadfile_elf.c
  ~ parse.y                               ~ virtio.c
  ~ vmd.h                                 ~ vmm.c

  > Introduce memory ranges to support VMs with >= 4G RAM
  > Kernel bits:
  > - When creating a VM, a list of memory ranges has to be specified,
  > similar to the BIOS memory map. This is necessary for VMs with
  > RAM sizes approaching 4G because we'll need PCI MMIO space in
  > the higher parts of the 32 bit address space.
  > vmctl and vmd bits:
  > - Construct appropriate memory ranges to create a VM with a given
  > RAM size
  > - Construct a corresponding BIOS memory map from the memory ranges
  > and update the boot params page accordingly.
  > - Make sure that all variables that represent guest physical addresses
  > match the address width of the target CPU instead of using uint32_t.
  > - Fix some integer promotion glitches that actually restricted VM
  > RAM size to 2G.
  > This changes the VM create ioctl interface, so update your kernel,
  > vmd, and vmctl.
  > ok mlarkin@ (stefan@)

===============================================================================
_______________________________________________
odc mailing list
[email protected]
http://www.squish.net/mailman/listinfo/odc

Reply via email to