BSD Commit Log Search

   regen

   add Intel Wildcat Lake Ethernet ids

   fix up synopsis and tweak wording for -Z

   document existence of mlkem768{brainpoolp256r1,nistp256}-sha256 KEXes

   switch aarch64 CPU feature detection to elf_aux_info()

   ok kettenis@ tb@

   libsa: drop prototypes for functions not implemented in libsa

   ok tb@

   Switch type of imsgbuf_get return variable 'n' to int.

   Addtionally switch the type of a write return variable to ssize_t.
   OK dv@

   Remove \n at end of log_debug(), not needed.

   OK dv@

   Use the right type for the return value of imsgbuf_get and imsgbuf_read

   ok florian@ rsadowski@

   Adjust type of 'n' used by imsgbuf_get and imsgbuf_read to int.

   Additionally stop abusing 'n' for other means and use better variables
   for those cases.

   OK tb@

   rpki-client: unexpectedely -> unexpectedly

   ok claudio

   rpki-client: zap extraneous empty line in http.c

   When using the high-level FUSE API, the filesystem may choose between
   two modes of operation when implementing readdir().

   1) The readdir implementation ignores the offset parameter, and
      passes zero to the filler function's offset. The filler function
      will not return '1' (unless an error happens), so the whole
      directory is read in a single readdir operation.

   2) The readdir implementation keeps track of the offsets of the
      directory entries. It uses the offset parameter and always passes
      non-zero offset to the filler function. When the buffer is full
      (or an error happens) the filler function will return '1'.

   We currently don't support 1) and instead implement an alternative
   mode that is stateless but emulates the behaviour. For each
   FUSE_READDIR received from the kernel, it will invoke the file
   system's readdir() callback and ask it to completely fill the buffer
   again, but ignore any entries that are before the given offset or
   exceed the size of the buffer. This of course has a performance

    [11 lines not shown]

   convert pointless bitfield to a regular variable; ok krw

   Switch over to imsgbuf_get() from imsg_get(), nothing uses the return
   value as message length.

   OK tb@

   Switch from imsg_get to imsgbuf_get and switch 'n' from ssize_t to int.

   OK tb@

   Switch from imsg_get to imsgbuf_get.

   OK tb@

   Switch from imsg_get() to imsgbuf_get(), the return value is not used
   for its size. Also switch type of n to int.

   OK tb@

   Switch from imsg_get to imsgbuf_get and switch type of n to int.

   OK tb@

   Switch from imsg_get to imsgbuf_get.

   OK tb@

   Adjust type of 'n' from ssize_t to int since imsgbuf_get() now returns int
   and so does imsgbuf_read().

   OK florian@

   Remove \n from log message. log_debug already adds that internally.

   OK florian@

   Adjust type of 'n' from ssize_t to int since imsgbuf_get() now returns int
   and so does imsgbuf_read().

   OK florian@

   Adjust type of 'n' from ssize_t to int since imsgbuf_get() now returns int
   and so does imsgbuf_read().

   OK florian@

   Remove \n from log messages.

   OK florian@

   Adjust type of 'n' to int since imsgbuf_get now returns int and so
   does imsgbuf_read where 'n' is used as well.

   OK florian@

   Do not attempt to drain write buffer on stuck clients, since it requires
   a weird dance to make libevent do it. Instead, just ignore the client
   and destroy the buffer normally if not drained in 10 seconds.

   sndiod: Replace {OPT,APP,PORT,MIDITHRU}_NAMEMAX by CTL_NAMEMAX

   All are defined to the same value, so no object change.

   sndiod: Define OPT_NAMEMAX to the string size, \0 included

   This is less error prone. No object change.

   Incorporate new RTR v2 error codes from draft-ietf-sidrops-8210bis-26

   RTR v2 introduces additional error codes:

    9: ASPA Provider List Error (fatal): The received ASPA PDU has an
       incorrect list of Provider Autonomous System Numbers.
   10: Transport Error (fatal): An error such as a stall or other transport
       layer failure occurred.
   11: Ordering Error (fatal): The received PDU does not conform with the
       specification defined ordering.
   12: Cache Restart (non-fatal): The cache is restarting.
   13: Cache Shutdown (fatal): The cache has shut down deliberately.

   OK claudio@