[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1358574847.3464.422.camel@edumazet-glaptop>
Date: Fri, 18 Jan 2013 21:54:07 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Eric Wong <normalperson@...t.net>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Willy Tarreau <w@....eu>
Subject: Re: splice() giving unexpected EOF in 3.7.3 and 3.8-rc4+
On Sat, 2013-01-19 at 04:49 +0000, Eric Wong wrote:
> With the following flow, I'm sometimes getting an unexpected EOF on the
> pipe reader even though I never close the pipe writer:
>
> tcp_wr -write-> tcp_rd -splice-> pipe_wr -> pipe_rd -splice-> /dev/null
>
> I encounter this in in 3.7.3, 3.8-rc3, and the latest from Linus
> 3.8-rc4+(5da1f88b8b727dc3a66c52d4513e871be6d43d19)
>
> It takes longer (about 20s) to reproduce this issue on my KVM (2 cores)
> running the latest Linus kernel, so maybe real/faster hardware is needed.
> My dual-core laptop (on 3.7.3) which hosts the VM does encounter this
> issue within a few seconds (or even <1s).
>
> Using schedtool to pin to a single core (any CPU core) on real hardware
> seems to avoid this issue on real hardware. Not sure how KVM uses CPUs,
> but schedtool doesn't help inside my VM (not even schedtool on the KVM
> process).
>
> Example code below (and via: git clone git://bogomips.org/spliceeof )
>
> Expected outout from ./spliceeof:
> done writing
> splice(in) EOF (expected)
>
> Output I get from ./spliceeof:
> splice(out) EOF (UNEXPECTED)
> in left: 47716 # the byte value varies
>
> I've successfully run similar code within the past year on some 3.x
> kernels, so I think this issue is fairly recent (Cc-ing folks who
> have touched splice lately).
>
> Any likely candidates before I start bisection? Thanks for reading.
>
> -------------------------------- 8< ------------------------------
Hmm, this might be already fixed in net-next tree, could you try it ?
Thanks !
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists