From: Milan Broz <mbroz@redhat.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: device-mapper development <dm-devel@redhat.com>,
davem@davemloft.net, linux-crypto@vger.kernel.org
Subject: Re: Re: NULL data pointer dereference in kcryptd
Date: Sat, 01 Aug 2009 11:04:11 +0200 [thread overview]
Message-ID: <4A74050B.6080608@redhat.com> (raw)
In-Reply-To: <20090801002708.GA6292@gondor.apana.org.au>
Herbert Xu wrote:
> On Fri, Jul 31, 2009 at 10:54:45PM +0200, Michael Buesch wrote:
>> [15577.988608] NIP [c0000000000b8034] .mempool_alloc+0x74/0x1a0
>> [15577.988614] LR [c000000000139bdc] .bio_alloc_bioset+0x4c/0x130
>> [15577.988616] Call Trace:
>> [15577.988619] [c0000001f022fb60] [c0000001f022fbf0] 0xc0000001f022fbf0 (unreliable)
>> [15577.988625] [c0000001f022fc40] [c000000000139bdc] .bio_alloc_bioset+0x4c/0x130
>> [15577.988632] [c0000001f022fcf0] [c0000000005334a0] .kcryptd_crypt+0x210/0x520
>> [15577.988637] [c0000001f022fde0] [c000000000068018] .worker_thread+0x248/0x3e0
>> [15577.988642] [c0000001f022ff00] [c00000000006e1e4] .kthread+0x84/0xe0
>> [15577.988648] [c0000001f022ff90] [c000000000021830] .kernel_thread+0x54/0x70
That seems like mempool is NULL in bio_alloc_bioset. That mempool/bioset is destroyed only
when crypt mapping is destroyed, after workqueue is flushed, so it should not happen...
Which command did you exactly run to trigger this? only sync & mkfs on existing
LUKS device or there was also some cryptsetup luksClose (or something removing
mapping) before?
> kcryptd actually belongs to drivers/md/dm-crypt.c. So please post
> to the DM list.
yes, this is dm-crypt or block layer problem. But I read linux-crypto list too:-)
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2009-08-01 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 20:54 NULL data pointer dereference in kcryptd Michael Buesch
2009-08-01 0:27 ` Herbert Xu
2009-08-01 9:04 ` Milan Broz [this message]
2009-08-01 10:07 ` [dm-devel] " Michael Buesch
2009-08-01 11:09 ` Michael Buesch
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=4A74050B.6080608@redhat.com \
--to=mbroz@redhat.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.