OpenBSD src changes summary for 2016-07-27
==========================================

regress/usr.sbin                        sbin/sysctl
share/man                               sys/arch/amd64/amd64
sys/arch/arm/arm                        sys/arch/arm/armv7
sys/arch/arm/include                    sys/arch/arm/simplebus
sys/arch/armv7/imx                      sys/arch/armv7/omap
sys/arch/armv7/sunxi                    sys/arch/octeon/dev
sys/arch/sparc/sparc                    sys/arch/sparc64/sparc64
sys/dev/acpi                            sys/dev/ofw
sys/dev/pv                              sys/sys
sys/uvm                                 usr.bin/printf
usr.bin/ssh                             usr.bin/vmstat
usr.bin/yacc                            usr.sbin/httpd
usr.sbin/pkg_add                        usr.sbin/relayd

== regress =========================================================== 01/06 ==

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

usr.sbin

  + relayd/args-http-host.pl              + relayd/args-http-host2.pl
  + relayd/args-http-host3.pl             + relayd/args-http-host4.pl

  > Improve parsing of the Host by following RFC 7230 Section 5.4 more
  > strictly:
  > - Respond with a 400 (Bad Request) if there is more than one Host:
  > header to prevent ambiguities.
  > - Make sure that the host in the optional absolute form of
  > request-target (eg. GET http://www.target.com/ HTTP/1.1) matches the
  > Host: value.  Proxies are supposed to ignore the Host: value if the
  > request-target exists, but relayd used to ignore the absolute
  > request-target form instead.  In HTTP terminology, relayd is a gateway
  > and not a proxy, but it has to make sure that the host is validated
  > consistently.
  > OK benno@ bluhm@ (reyk@)

== sbin ============================================================== 02/06 ==

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

sysctl

  ~ sysctl.c                              

  > increase the size of forkstat fields to accomodate large values (tedu@)

  ~ sysctl.8                              

  > correct syntax for baddynamic example. from Holger Mikolon (tedu@)

== share ============================================================= 03/06 ==

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

man

  ~ man9/srp_enter.9                      

  > Missing word ("no"). (jca@)

  ~ man9/socreate.9                       

  > document the so_upcall option to socreate (phessler@)

== sys =============================================================== 04/06 ==

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

arch/amd64/amd64

  ~ mem.c                                 

  > improve comments a bit. ok mlarkin tom (tedu@)

arch/arm/arm

  ~ pmap7.c                               

  > When pmap_page_remove() is called by UVM, a physical page is to be
  > removed from pmaps it currently is in.  To check if a virtual address
  > pointing to that physical page has been mapped, the code uses
  > the l2pte_valid() function.  Unfortunately there is a difference
  > between being valid and the PTE being zero.  If a page is mapped
  > but has never been accessed, it will be non-zero but invalid.
  > In that case the PTE for that virtual address will not be zeroed
  > and the virtual address will be removed from the vm page struct.
  > The next time someone tries to map a page to that virtual address,
  > other pmap code will consider the virtual address to be already
  > mapped, even though that assumption is completely wrong.
  > To make sure this does not happen, check the PTE for zero.  This way
  > the PTE will be zeroed correctly.  The check for zero is how other
  > ARM pmap code also handles this issue.
  > ok kettenis@ tom@ (patrick@)

arch/arm/armv7

  ~ armv7_space.c                         

  > Remove a feature to re-use existing early bootstrap mappings. This
  > allowed you to pass a virtual address, which you received from an
  > early bootstrap mapping, as physical address to bus_space_map(9).
  > It breaks bus_space_map(9) for peripherals that are after 0xC0000000,
  > as it assumes that everything after that address cannot be a real
  > peripheral.  But that's wrong.  It does not make sense to pass a
  > virtual address to bus_space_map(9) anyway, so just get rid of this
  > whole "feature".
  > ok kettenis@ (patrick@)

arch/arm/include

  ~ fdt.h                                 

  > Instead of passing the raw reg property to simplebus nodes,
  > pass a pre-processed array of fdt_reg structs.  This means
  > that the drivers don't have to understand the cell properties
  > themselves but can rely on the 64-bit addr/size pairs.
  > ok kettenis@ (patrick@)

arch/arm/simplebus

  ~ simplebus.c                           

  > Instead of passing the raw reg property to simplebus nodes,
  > pass a pre-processed array of fdt_reg structs.  This means
  > that the drivers don't have to understand the cell properties
  > themselves but can rely on the 64-bit addr/size pairs.
  > ok kettenis@ (patrick@)

arch/armv7/imx

  ~ if_fec.c                              ~ imxahci.c
  ~ imxdog.c                              ~ imxehci.c
  ~ imxesdhc.c                            ~ imxgpio.c
  ~ imxiic.c                              ~ imxuart.c

  > Instead of passing the raw reg property to simplebus nodes,
  > pass a pre-processed array of fdt_reg structs.  This means
  > that the drivers don't have to understand the cell properties
  > themselves but can rely on the 64-bit addr/size pairs.
  > ok kettenis@ (patrick@)

arch/armv7/omap

  ~ if_cpsw.c                             ~ omap_com.c
  ~ omdog.c                               ~ ommmc.c
  ~ ti_iic.c                              

  > Instead of passing the raw reg property to simplebus nodes,
  > pass a pre-processed array of fdt_reg structs.  This means
  > that the drivers don't have to understand the cell properties
  > themselves but can rely on the 64-bit addr/size pairs.
  > ok kettenis@ (patrick@)

arch/armv7/sunxi

  ~ sxie.c                                ~ sxiuart.c

  > Instead of passing the raw reg property to simplebus nodes,
  > pass a pre-processed array of fdt_reg structs.  This means
  > that the drivers don't have to understand the cell properties
  > themselves but can rely on the 64-bit addr/size pairs.
  > ok kettenis@ (patrick@)

  ~ sunxi.c                               

  > Get interrupts going for the Allwinner-R8 chip.
  > ok kettenis@, patrick@ (mglocker@)

arch/octeon/dev

  ~ octeon_uartbus.c                      

  > Remove unnecessary remapping of registers.
  > ok jasper@ (visa@)

arch/sparc/sparc

  ~ mem.c                                 

  > ansify mem.c to the latest fashion. with a fix from mike burns. ok deraadt
  > (tedu@)

arch/sparc64/sparc64

  ~ mem.c                                 

  > ansify mem.c to the latest fashion. with a fix from mike burns. ok deraadt
  > (tedu@)

dev/acpi

  ~ acpicbkbd.c                           

  > after system resume, re-write backlight level (jcs@)

dev/ofw

  ~ ofw_gpio.c                            ~ ofw_gpio.h

  > Add interface to facilitate iterating over gpios.
  > ok patrick@ (kettenis@)

dev/pv

  ~ if_hvn.c                              

  > zero sizeof a struct not sizeof the pointer to it
  > ok mikeb@ (jsg@)

sys

  ~ vmmeter.h                             

  > increase the size of forkstat fields to accomodate large values (tedu@)

uvm

  ~ uvm_amap.c                            

  > check flags with mask instead of equality, in case we decide to mix
  > another flag in at some point. ok stefan (tedu@)

== usr.bin =========================================================== 05/06 ==

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

printf

  ~ printf.c                              

  > fix signed char extension bugs. from [email protected]. ok guenther.
  > As a personal remark, I'll add that it's not necessary to cast a value
  > to a function's return type. The compiler is happy to do that for you.
  > But such casts can hide warnings and bugs. (tedu@)

ssh

  ~ atomicio.c                            

  > better bounds check on iovcnt (we only ever use fixed, positive values)
  > (djm@)

vmstat

  ~ vmstat.c                              

  > increase the size of forkstat fields to accomodate large values (tedu@)

yacc

  ~ main.c                                ~ yacc.1

  > it should not be necessary for yacc to use TMPDIR, /tmp is good enough.
  > ok beck deraadt guenther (tedu@)

== usr.sbin ========================================================== 06/06 ==

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

httpd

  ~ server_http.c                         

  > According to RFC 7231 4.3.7, OPTIONS may have body. "Although this
  > specification does not define any use for such a payload, future
  > extensions to HTTP might use the OPTIONS body to make more detailed
  > queries about the target resource." The future has arrived.
  > Found and tested by Michael Lechtermann
  > OK benno@ (reyk@)

pkg_add

  ~ OpenBSD/PackageRepository.pm          

  > hunting around for some sporadic error message. Removing the hash entry
  > entirely is slightly better.
  > noticed by sthen@ (espie@)

  ~ pkg_info.1                            ~ OpenBSD/PkgInfo.pm

  > don't include firmwares in the fuzzy auto-reinstall list (espie@)

  ~ OpenBSD/PackingList.pm                

  > checking for firmware works better if I pass thru all options (espie@)

relayd

  ~ relay_http.c                          ~ relayd.c
  ~ relayd.h                              

  > Improve parsing of the Host by following RFC 7230 Section 5.4 more
  > strictly:
  > - Respond with a 400 (Bad Request) if there is more than one Host:
  > header to prevent ambiguities.
  > - Make sure that the host in the optional absolute form of
  > request-target (eg. GET http://www.target.com/ HTTP/1.1) matches the
  > Host: value.  Proxies are supposed to ignore the Host: value if the
  > request-target exists, but relayd used to ignore the absolute
  > request-target form instead.  In HTTP terminology, relayd is a gateway
  > and not a proxy, but it has to make sure that the host is validated
  > consistently.
  > OK benno@ bluhm@ (reyk@)

  ~ relay_http.c                          

  > According to RFC 7231 4.3.7, OPTIONS may have body. "Although this
  > specification does not define any use for such a payload, future
  > extensions to HTTP might use the OPTIONS body to make more detailed
  > queries about the target resource." The future has arrived.
  > Found and tested by Michael Lechtermann
  > OK benno@ (reyk@)

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

Reply via email to