From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com, Ondrej Mosnacek <omosnacek@gmail.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev
Subject: Re: Regression bisected to "crypto: af_alg: Convert af_alg_sendpage() to use MSG_SPLICE_PAGES"
Date: Tue, 04 Jul 2023 10:41:45 +0100 [thread overview]
Message-ID: <1361504.1688463705@warthog.procyon.org.uk> (raw)
In-Reply-To: <ZKPgkgiddAl9qddT@gondor.apana.org.au>
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> All it's saying is that if you modify the data after sending it off
> via splice then the data that will be on the wire is undefined.
Er, no. It can literally remove the page from the process's VM and paste it
somewhere else - though in this case, that shouldn't happen. However, the
buffer passed to SPLICE_F_GIFT should also be page-aligned, which it might not
be because they used calloc().
There's no reason to use SPLICE_F_GIFT here. vmsplice() still attaches the
> There is no reason why this should crash.
Agreed. I'm still looking at it. Interestingly, the output comes out the
same, no matter whether vmsplice(), vmsplice() + SPLICE_F_GIFT or writev(), so
it looks like the buffers get to
> If we can't fix this the patches should be reverted.
I didn't change vmsplice() or the way pages are stored in the pipe.
And, note, there are also a bunch of GUP changes that could have an effect.
David
next prev parent reply other threads:[~2023-07-04 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:21 Regression bisected to "crypto: af_alg: Convert af_alg_sendpage() to use MSG_SPLICE_PAGES" Ondrej Mosnáček
2023-07-04 8:50 ` David Howells
2023-07-04 9:04 ` Herbert Xu
2023-07-04 9:41 ` David Howells [this message]
2023-07-04 10:10 ` Herbert Xu
2023-07-04 8:59 ` David Howells
2023-07-04 14:34 ` David Howells
2023-07-04 15:53 ` David Howells
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=1361504.1688463705@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnacek@gmail.com \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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