OpenBSD src changes summary for 2016-06-09
==========================================

share/man                               sys/arch/arm/include
sys/arch/arm/simplebus                  sys/arch/armv7/conf
sys/arch/armv7/imx                      sys/arch/octeon/dev
sys/netinet                             usr.sbin/ldpd

== share ============================================================= 01/03 ==

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

man

  ~ man8/afterboot.8                      

  > In afterboot(8), replace le0 with em0. lo0 and le0 are too close with tiny
  > font.
  > ok jmc mpi kettenis deraadt (stsp@)

== sys =============================================================== 02/03 ==

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

arch/arm/include

  ~ fdt.h                                 

  > Fetch "reg" and "interrupts" properties and pass them down as attach args
  > to
  > our children.
  > ok jsg@ (kettenis@)

arch/arm/simplebus

  ~ simplebus.c                           

  > Fetch "reg" and "interrupts" properties and pass them down as attach args
  > to
  > our children.
  > ok jsg@ (kettenis@)

arch/armv7/conf

  ~ GENERIC                               

  > Dynamically attach i.MX6 ahci(4) using the FDT.
  > ok jsg@ (kettenis@)

  ~ GENERIC                               

  > Dynamically attach imxesdhc(4) using the FDT.
  > ok jsg@ (kettenis@)

arch/armv7/imx

  ~ imxiic.c                              

  > Make use of the information about the node passed down to us by
  > simplebus(4).
  > ok jsg@ (kettenis@)

  ~ files.imx                             ~ imx.c
  ~ imxahci.c                             

  > Dynamically attach i.MX6 ahci(4) using the FDT.
  > ok jsg@ (kettenis@)

  ~ files.imx                             ~ imx.c
  ~ imxesdhc.c                            

  > Dynamically attach imxesdhc(4) using the FDT.
  > ok jsg@ (kettenis@)

arch/octeon/dev

  ~ cn30xxgmx.c                           ~ cn30xxgmxreg.h
  ~ cn30xxgmxvar.h                        ~ cn30xxpip.c

  > Add SGMII support and PHY addresses for 8-port EdgeRouters. This makes
  > plain RJ45 ports eth[4-7] usable.
  > ok dlg@, tested by martijn@ (visa@)

netinet

  ~ tcp_input.c                           

  > Fix typo in comment.  From Kapetanakis Giannis (bluhm@)

== usr.sbin ========================================================== 03/03 ==

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

ldpd

  ~ adjacency.c                           ~ hello.c
  ~ interface.c                           ~ ldpe.c
  ~ ldpe.h                                

  > Send a fatal notification when the last hello adjacency is deleted.
  > RFC 5036 says:
  > "When the last Hello adjacency for an LDP session is
  > deleted, the LSR terminates the LDP session by sending a Notification
  > message and closing the transport connection".
  > Send a "Hold Timer Expired" notification when the triggering event is
  > a hello hold time timeout. In the other cases, like disabling LDP on an
  > interface, send a "Shutdown" notification instead.
  > Before this patch we were just closing the neighbor's transport
  > connection.
  > Fixes the following ANVL LDP tests: 7.17 and 23.3. (renato@)

  ~ packet.c                              

  > Do not shut down the session upon receiving unknown messages.
  > RFC 5036 says the following about the receipt of unknown messages:
  > "Unknown message bit.  Upon receipt of an unknown message, if U is
  > clear (=0), a notification is returned to the message originator;
  > if U is set (=1), the unknown message is silently ignored".
  > We were correctly ignoring unknown messages when the U-bit was set. But
  > when this bit was not set, we were shutting down the session when the
  > correct thing to do is to just send a non-fatal notification message.
  > Fix IxANVL LDP test 22.13. (renato@)

  ~ packet.c                              

  > Do set the Message ID for Hello messages too.
  > In the original LDP specification, there was no circumstance where a
  > Notification message could be sent in response to a Hello message. So
  > setting the Message ID field for Hello packets was useless.
  > This changed with RFC 7552, where Hello packets can trigger the "Transport
  > Connection Mismatch" notification when the local and remote transport
  > preferences doesn't match. In this case, having a meaningful Message ID
  > in the Hello packets can aid in testing and troubleshooting. (renato@)

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

Reply via email to