From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: linux-crypto@vger.kernel.org, David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] scatterlist: introduce sg_nents_for_len
Date: Wed, 3 Jun 2015 13:09:06 +0800 [thread overview]
Message-ID: <20150603050906.GC3884@gondor.apana.org.au> (raw)
In-Reply-To: <20150601161519.729.75909.stgit@tlendack-t1.amdoffice.net>
On Mon, Jun 01, 2015 at 11:15:19AM -0500, Tom Lendacky wrote:
> This series introduces and makes use of a new scatterlist function named
> sg_nents_for_len. The purpose of this function is determine the number
> of scatterlist entries required to satisify a specified length. The
> resulting count can be used as input to the dma_map_sg function to map
> only the entries needed.
>
> This function is needed for cases where a supplied scatterlist has not
> marked the last filled sg entry as the end of the scatterlist. In these
> cases, the sg_nents function count includes sg entries that may not have
> been filled in. When using this value in a dma_map_sg call it can result
> in errors/bugs being generated.
>
> The following patches are included in this series:
> - Introduce the sg_nents_for_len function
> - Update the ccp driver to use the sg_nents_for_len function
>
> This patch series is based on cryptodev-2.6.
Both applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2015-06-03 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 16:15 Tom Lendacky
2015-06-01 16:15 ` [PATCH v1 1/2] " Tom Lendacky
2015-06-01 16:15 ` [PATCH v1 2/2] crypto: ccp - Protect against poorly marked end of sg list Tom Lendacky
2015-06-03 5:09 ` Herbert Xu [this message]
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=20150603050906.GC3884@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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
all inboxes | Powered by JetHome®