From: David Miller <davem@davemloft.net>
To: gnault@redhat.com
Cc: netdev@vger.kernel.org, linux-api@vger.kernel.org,
edumazet@google.com, mleitner@redhat.com, pabeni@redhat.com
Subject: Re: [PATCH net-next] sock: consistent handling of extreme SO_SNDBUF/SO_RCVBUF values
Date: Sat, 16 Feb 2019 18:10:50 -0800 (PST) [thread overview]
Message-ID: <20190216.181050.693622468464700230.davem@davemloft.net> (raw)
In-Reply-To: <2cb69b6987b6e23f8b8c1aa8dc524efa6bd53191.1550026643.git.gnault@redhat.com>
From: Guillaume Nault <gnault@redhat.com>
Date: Wed, 13 Feb 2019 04:30:34 +0100
> SO_SNDBUF and SO_RCVBUF (and their *BUFFORCE version) may overflow or
> underflow their input value. This patch aims at providing explicit
> handling of these extreme cases, to get a clear behaviour even with
> values bigger than INT_MAX / 2 or lower than INT_MIN / 2.
...
> Signed-off-by: Guillaume Nault <gnault@redhat.com>
Thank you so much for writing such a detailed commit message.
Applied.
prev parent reply other threads:[~2019-02-17 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 3:30 [PATCH net-next] sock: consistent handling of extreme SO_SNDBUF/SO_RCVBUF values Guillaume Nault
2019-02-17 2:10 ` David Miller [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190216.181050.693622468464700230.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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