LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vasily.isaenko@oracle.com
Subject: Re: [PATCH] net: sysctl_net_core: check SNDBUF and RCVBUF for min length
Date: Wed, 11 Mar 2015 06:25:08 -0700 [thread overview]
Message-ID: <1426080308.11398.37.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <1426073357-6211-1-git-send-email-alexey.kodanev@oracle.com>
On Wed, 2015-03-11 at 14:29 +0300, Alexey Kodanev wrote:
> sysctl has sysctl.net.core.rmem_*/wmem_* parameters which can be
> set to incorrect values. Given that 'struct sk_buff' allocates from
> rcvbuf, incorrectly set buffer length could result to memory
> allocation failures. For example, set them as follows:
>
> # sysctl net.core.rmem_default=64
> net.core.wmem_default = 64
> # sysctl net.core.wmem_default=64
> net.core.wmem_default = 64
> # ping localhost -s 1024 -i 0 > /dev/null
>
Yeah, root users seem to act like monkeys these days ;)
Note the real bug is in unix_stream_sendmsg(), as it assumes
sk_sndbuf > 130 :
/* Keep two messages in the pipe so it schedules better */
size = min_t(int, size, (sk->sk_sndbuf >> 1) - 64);
The 64 here seems to assume skb overhead of linux 0.1 on a hypothetical
16bit host ;)
I guess your fix is fine, but might break applications that were
expecting that sysctl net.core.wmem_default=512 would effectively limit
queue occupancy to one skb (without crashing unix_stream_sendmsg())
As commit eea86af6b1e18d6fa did not trigger bug reports, I think we
should get your patch, and eventually adjust SOCK_MIN_SNDBUF if required
later.
Note that we should also limit max value, because of possible arithmetic
overflows for sk->sk_wmem_alloc.
A max of (1U << 31) might be reasonable ?
next prev parent reply other threads:[~2015-03-11 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 11:29 [PATCH] net: sysctl_net_core: check SNDBUF and RCVBUF for min length Alexey Kodanev
2015-03-11 13:25 ` Eric Dumazet [this message]
2015-03-12 1:25 ` David Miller
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=1426080308.11398.37.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=alexey.kodanev@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vasily.isaenko@oracle.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;
as well as URLs for NNTP newsgroup(s).