From: Milan Broz <mbroz@redhat.com>
To: Wesley Leggette <wleggette@kaylix.net>
Cc: linux-kernel@vger.kernel.org, Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: Kernel panic in kcryptd
Date: Thu, 30 Oct 2008 20:04:04 +0100 [thread overview]
Message-ID: <490A0524.70406@redhat.com> (raw)
In-Reply-To: <F18563A1-0A44-4790-A2AA-68D1A60030E6@kaylix.net>
Wesley Leggette wrote:
>> Snapshots involved in LVM
>>>
>>> Is it reproducible without snapshots involved?
>> Will try. I'm trying to reproduce right now without "bigmem", but
>> will stop if that is likely not the case.
>>
>
> Also, I should mention that I'm trying this now (without bigmem) on a
> logical volume that doesn't have snapshots. Would this make a
> difference even if there are other lv's with snapshots (if they are
> not being used)?
I think that if there is no IOs running over snapshots, it should be ok
for the first try. There is too many layers involved...
Maybe it is related to to http://bugzilla.kernel.org/show_bug.cgi?id=11636
Milan
prev parent reply other threads:[~2008-10-30 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 16:02 Kernel panic in kcryptd Wesley Leggette
2008-10-30 18:30 ` Milan Broz
2008-10-30 18:34 ` Wesley Leggette
2008-10-30 18:37 ` Wesley Leggette
2008-10-30 19:04 ` Milan Broz [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=490A0524.70406@redhat.com \
--to=mbroz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=wleggette@kaylix.net \
/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