From: "J. Bruce Fields" <bfields@fieldses.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: [PATCH] crypto: scatterwalk_copychunks() fails to advance through scatterlist
Date: Tue, 20 Mar 2007 17:17:51 -0400 [thread overview]
Message-ID: <20070320211751.GC16930@fieldses.org> (raw)
In-Reply-To: <20070320205421.GA23929@gondor.apana.org.au>
On Wed, Mar 21, 2007 at 07:54:21AM +1100, Herbert Xu wrote:
> On Tue, Mar 20, 2007 at 10:16:14AM -0400, J. Bruce Fields wrote:
> >
> > Are the elements of the scatterlists assumed to always be full pages? I
>
> Definitely not.
>
> > need to encrypt things that look like, for example:
> >
> > sg[0].page = page1
> > sg[0].offset = 0
> > sg[0].length = 5
> > sg[1].page = page2
> > sg[1].offset = 0
> > sg[1].length = 37
>
> OK I see what you mean now. I'll apply your patch.
Thanks!
By the way, the commit that I believe introduced this regression did two
or three different things at once--I spent some time staring at it and
can't say I really understand the change. That's probably just me! But
would it be possible to split up these patches fine enough that people
inexperienced with this code would have a better chance of understanding
what's going on?
There's so many potential corner cases to handle here, I know I'd want
to tread very carefully....
(And did the crypto testing module use to have some tests for buffers
that were fragmented in odd ways, or was I imagining that? I'd be happy
to help come up with some test cases if it'd be useful.)
--b.
next prev parent reply other threads:[~2007-03-20 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 23:55 [PATCH] crypto: scatterwalk_copychunks() fails to advance through scatterlist J. Bruce Fields
2007-03-20 5:16 ` Herbert Xu
2007-03-20 14:16 ` J. Bruce Fields
2007-03-20 14:17 ` J. Bruce Fields
2007-03-20 20:54 ` Herbert Xu
2007-03-20 21:17 ` J. Bruce Fields [this message]
2007-03-20 22:04 ` Herbert Xu
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=20070320211751.GC16930@fieldses.org \
--to=bfields@fieldses.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=nfsv4@linux-nfs.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