public inbox for
help / color / mirror / Atom feed
From: Sebastian Huber <>
Subject: [newlib-cygwin] SO_RERROR indicates that receive buffer overflows
Date: Mon, 11 Jul 2022 11:53:54 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=2ba2e1e052fee6fcde09efc1aacd29a83de366a3

commit 2ba2e1e052fee6fcde09efc1aacd29a83de366a3
Author: Alexander V. Chernikov <>
Date:   Sun Feb 7 17:21:18 2021 +0000

    SO_RERROR indicates that receive buffer overflows
    should be handled as errors. Historically receive buffer overflows have been
    ignored and programs could not tell if they missed messages or messages had
    been truncated because of overflows. Since programs historically do not expect
    to get receive overflow errors, this behavior is not the default.
    This is really really important for programs that use route(4) to keep in sync
    with the system. If we loose a message then we need to reload the full system
    state, otherwise the behaviour from that point is undefined and can lead
    to chasing bogus bug reports.

 newlib/libc/sys/rtems/include/sys/socket.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/newlib/libc/sys/rtems/include/sys/socket.h b/newlib/libc/sys/rtems/include/sys/socket.h
index 4079b3e91..54cd0be93 100644
--- a/newlib/libc/sys/rtems/include/sys/socket.h
+++ b/newlib/libc/sys/rtems/include/sys/socket.h
@@ -139,6 +139,7 @@ typedef	__uintptr_t	uintptr_t;
 #define	SO_NO_OFFLOAD	0x00004000	/* socket cannot be offloaded */
 #define	SO_NO_DDP	0x00008000	/* disable direct data placement */
 #define	SO_REUSEPORT_LB	0x00010000	/* reuse with load balancing */
+#define	SO_RERROR	0x00020000	/* keep track of receive errors */
  * Additional options, not kept in so_options.

                 reply	other threads:[~2022-07-11 11:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).