From: Jorgen Lundman <lundman@lundman.net>
To: linux-crypto@vger.kernel.org
Subject: Re: Crypto causes panic in scatterwalk_done with large/multiple buffers
Date: Sun, 18 Nov 2012 11:10:39 +0900 [thread overview]
Message-ID: <50A8439F.4060201@lundman.net> (raw)
In-Reply-To: <50A82BD1.4000505@lundman.net>
Specifically, the crash I get is finally in here:
static void Xscatterwalk_pagedone(struct scatter_walk *walk, int out,
unsigned int more)
{
if (out) {
struct page *page;
page = sg_page(walk->sg) + ((walk->offset - 1) >> PAGE_SHIFT);
printk("**** PageSlab: page %p offset 0x%04lx\n",
page, walk->offset);
if (!PageSlab(page)) { // <===== here
kernel: [ 62.650590] **** PageSlab: page ffffeb04000b7e40 offset 0x1000
Commenting out the call to PageSlab and flush_dcache_page(page);
surprisingly makes it work a little better. But presumably it comes with
a cost that I can not yet see.
next prev parent reply other threads:[~2012-11-18 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 9:03 Crypto causes panic in scatterwalk_done with large/multiple buffers Jorgen Lundman
2012-11-17 0:42 ` Jussi Kivilinna
2012-11-17 8:39 ` Jussi Kivilinna
2012-11-18 0:29 ` Jorgen Lundman
2012-11-18 2:10 ` Jorgen Lundman [this message]
2012-11-18 17:40 ` Jussi Kivilinna
2012-11-19 0:29 ` Jorgen Lundman
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=50A8439F.4060201@lundman.net \
--to=lundman@lundman.net \
--cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.