From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>
Subject: Re: sendfile from 9p fs into af_alg
Date: Wed, 23 Nov 2016 06:16:28 +0000 [thread overview]
Message-ID: <20161123061628.GN1555@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20161123045558.GA43893@ast-mbp.thefacebook.com>
On Tue, Nov 22, 2016 at 08:55:59PM -0800, Alexei Starovoitov wrote:
> On Wed, Nov 23, 2016 at 04:46:26AM +0000, Al Viro wrote:
> > On Tue, Nov 22, 2016 at 07:58:29PM -0800, Alexei Starovoitov wrote:
> > > Hi Al,
> > >
> > > it seems the following commit 523ac9afc73a ("switch default_file_splice_read() to use of pipe-backed iov_iter")
> > > breaks sendfile from 9p fs into af_alg socket.
> > > sendfile into af_alg is used by iproute2/tc.
> > > I'm not sure whether it's 9p or crypto or vfs problem, but happy to test any patches.
> >
> > Could you try -rc6 (or anything that contains 680bb946a1ae04, for that
> > matter)?
>
> already tested with that patch in the latest net-next. Still broken :(
Joy... Which transport are you using there? The interesting part is
whether it's zerocopy or non-zerocopy path in p9_client_read()...
next prev parent reply other threads:[~2016-11-23 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 3:58 sendfile from 9p fs into af_alg Alexei Starovoitov
2016-11-23 4:46 ` Al Viro
2016-11-23 4:55 ` Alexei Starovoitov
2016-11-23 6:16 ` Al Viro [this message]
2016-11-23 8:58 ` Alexei Starovoitov
2016-11-23 15:53 ` Al Viro
2016-11-23 16:29 ` Alexei Starovoitov
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=20161123061628.GN1555@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--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).