From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: xemul@parallels.com, mgorman@suse.de, netdev@vger.kernel.org,
stable@kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] skb: Propagate pfmemalloc on skb from head page only
Date: Thu, 14 Mar 2013 11:54:41 -0400 (EDT) [thread overview]
Message-ID: <20130314.115441.1016076054622568752.davem@davemloft.net> (raw)
In-Reply-To: <1363270569.29475.11.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 14 Mar 2013 15:16:09 +0100
> On Thu, 2013-03-14 at 17:29 +0400, Pavel Emelyanov wrote:
>> Hi.
>>
>> I'm trying to send big chunks of memory from application address space via
>> TCP socket using vmsplice + splice like this
>>
>> mem = mmap(128Mb);
>> vmsplice(pipe[1], mem); /* splice memory into pipe */
>> splice(pipe[0], tcp_socket); /* send it into network */
>>
>> When I'm lucky and a huge page splices into the pipe and then into the socket
>> _and_ client and server ends of the TCP connection are on the same host,
>> communicating via lo, the whole connection gets stuck! The sending queue
>> becomes full and app stops writing/splicing more into it, but the receiving
>> queue remains empty, and that's why.
>>
>> The __skb_fill_page_desc observes a tail page of a huge page and erroneously
>> propagates its page->pfmemalloc value onto socket (the pfmemalloc on tail pages
>> contain garbage). Then this skb->pfmemalloc leaks through lo and due to the
>>
>> tcp_v4_rcv
>> sk_filter
>> if (skb->pfmemalloc && !sock_flag(sk, SOCK_MEMALLOC)) /* true */
>> return -ENOMEM
>> goto release_and_discard;
>>
>> no packets reach the socket. Even TCP re-transmits are dropped by this, as skb
>> cloning clones the pfmemalloc flag as well.
>>
>> That said, here's the proper page->pfmemalloc propagation onto socket: we
>> must check the huge-page's head page only, other pages' pfmemalloc and mapping
>> values do not contain what is expected in this place. However, I'm not sure
>> whether this fix is _complete_, since pfmemalloc propagation via lo also
>> oesn't look great.
>>
>> Both, bit propagation from page to skb and this check in sk_filter, were
>> introduced by c48a11c7 (netvm: propagate page->pfmemalloc to skb), in v3.5 so
>> Mel and stable@ are in Cc.
>>
>> Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
...
> Acked-by: Eric Dumazet <edumazet@google.com>
Applied and queued up for -stable, thanks.
next prev parent reply other threads:[~2013-03-14 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 13:29 [PATCH] skb: Propagate pfmemalloc on skb from head page only Pavel Emelyanov
2013-03-14 14:16 ` Eric Dumazet
2013-03-14 14:23 ` Pavel Emelyanov
2013-03-14 14:34 ` Eric Dumazet
2013-03-14 14:36 ` Pavel Emelyanov
2013-03-14 15:54 ` David Miller [this message]
2013-03-14 14:28 ` Mel Gorman
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=20130314.115441.1016076054622568752.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mgorman@suse.de \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
--cc=xemul@parallels.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).