From: Milan Broz <mbroz@redhat.com>
To: Melchior FRANZ <melchior.franz@gmail.com>
Cc: linux-crypto@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>
Subject: Re: [2.6.28.5] dm/crypt oops: "unable to handle kernel NULL pointer dereference" (tainted)
Date: Wed, 11 Mar 2009 21:42:26 +0100 [thread overview]
Message-ID: <49B82232.2090802@redhat.com> (raw)
In-Reply-To: <200903111319.43778@rk-nord.at>
Melchior FRANZ wrote:
>
> umount ...
> cryptsetup remove ...
> losetup -d ...
>
> BUG: unable to handle kernel NULL pointer dereference at 00000004
> IP: [<c0158a75>] mempool_free+0xd/0x9a
...
Yes, I know about that problem and I am almost sure that
it is fixed by patch I sent there http://lkml.org/lkml/2009/3/5/63
Something changed in timing so probability of hitting that
bug apparently increased in the last kernel (the problem was there always:-)
I had asked Alasdair to queue that to dm queue for upstream...
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2009-03-11 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 12:19 [2.6.28.5] dm/crypt oops: "unable to handle kernel NULL pointer dereference" (tainted) Melchior FRANZ
2009-03-11 20:42 ` Milan Broz [this message]
2009-03-13 13:49 ` Alasdair G Kergon
2009-03-16 13:38 ` Melchior FRANZ
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=49B82232.2090802@redhat.com \
--to=mbroz@redhat.com \
--cc=agk@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=melchior.franz@gmail.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