From: Willy Tarreau <w@1wt.eu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tcp: splice: fix an infinite loop in tcp_read_sock()
Date: Fri, 11 Jan 2013 00:01:45 +0100 [thread overview]
Message-ID: <20130110230145.GC17390@1wt.eu> (raw)
In-Reply-To: <1357837570.27446.2285.camel@edumazet-glaptop>
Hi Eric,
On Thu, Jan 10, 2013 at 09:06:10AM -0800, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> commit 02275a2ee7c0 (tcp: don't abort splice() after small transfers)
> added a regression.
>
>
> [ 83.843570] INFO: rcu_sched self-detected stall on CPU
> [ 83.844575] INFO: rcu_sched detected stalls on CPUs/tasks: { 6} (detected by 0, t=21002 jiffies, g=4457, c=4456, q=13132)
> [ 83.844582] Task dump for CPU 6:
> [ 83.844584] netperf R running task 0 8966 8952 0x0000000c
> [ 83.844587] 0000000000000000 0000000000000006 0000000000006c6c 0000000000000000
> [ 83.844589] 000000000000006c 0000000000000096 ffffffff819ce2bc ffffffffffffff10
> [ 83.844592] ffffffff81088679 0000000000000010 0000000000000246 ffff880c4b9ddcd8
> [ 83.844594] Call Trace:
> [ 83.844596] [<ffffffff81088679>] ? vprintk_emit+0x1c9/0x4c0
> [ 83.844601] [<ffffffff815ad449>] ? schedule+0x29/0x70
> [ 83.844606] [<ffffffff81537bd2>] ? tcp_splice_data_recv+0x42/0x50
> [ 83.844610] [<ffffffff8153beaa>] ? tcp_read_sock+0xda/0x260
> [ 83.844613] [<ffffffff81537b90>] ? tcp_prequeue_process+0xb0/0xb0
> [ 83.844615] [<ffffffff8153c0f0>] ? tcp_splice_read+0xc0/0x250
> [ 83.844618] [<ffffffff814dc0c2>] ? sock_splice_read+0x22/0x30
> [ 83.844622] [<ffffffff811b820b>] ? do_splice_to+0x7b/0xa0
> [ 83.844627] [<ffffffff811ba4bc>] ? sys_splice+0x59c/0x5d0
> [ 83.844630] [<ffffffff8119745b>] ? putname+0x2b/0x40
> [ 83.844633] [<ffffffff8118bcb4>] ? do_sys_open+0x174/0x1e0
> [ 83.844636] [<ffffffff815b6202>] ? system_call_fastpath+0x16/0x1b
>
>
> if recv_actor() returns 0, we should stop immediately,
> because looping wont give a chance to drain the pipe.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Willy Tarreau <w@1wt.eu>
> ---
> net/ipv4/tcp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index 1ca2536..5f173dc 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -1482,7 +1482,7 @@ int tcp_read_sock(struct sock *sk, read_descriptor_t *desc,
> break;
> }
> used = recv_actor(desc, skb, offset, len);
> - if (used < 0) {
> + if (used <= 0) {
> if (!copied)
> copied = used;
> break;
Thanks for catching this one. I'm amazed we didn't notice it earlier,
I've been running my stress-test kernels with this patch applied since
we did it.
Willy
next prev parent reply other threads:[~2013-01-10 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 17:06 [PATCH] tcp: splice: fix an infinite loop in tcp_read_sock() Eric Dumazet
2013-01-10 22:37 ` David Miller
2013-01-10 23:01 ` Willy Tarreau [this message]
2013-01-10 23:05 ` Eric Dumazet
2013-01-10 23:21 ` Willy Tarreau
2013-01-10 23:48 ` Rick Jones
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=20130110230145.GC17390@1wt.eu \
--to=w@1wt.eu \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).