From: Patrick McHardy <kaber@trash.net>
To: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6.23 PATCH 07/18] dm io: fix panic on large request
Date: Wed, 18 Jul 2007 12:08:48 +0200 [thread overview]
Message-ID: <469DE6B0.60807@trash.net> (raw)
In-Reply-To: <469D40BB.3030809@ce.jp.nec.com>
Jun'ichi Nomura wrote:
> Patrick McHardy wrote:
>
>>Jun'ichi Nomura wrote:
>>
>>>Are you using other dm modules such as dm-multipath, dm-mirror
>>>or dm-snapshot?
>>>If so, can you take the output of 'dmsetup table' and 'dmsetup ls'?
>>
>>No other modules.
>>
>>
>>>Do you have a reliable way to reproduce the oops which I can try?
>>
>>"/etc/init.d/cryptdisk start" (debian) on a luks partition triggered
>>it for me.
>
>
> With today's git HEAD (commit 49c13b51a15f1ba9f6d47e26e4a3886c4f3931e2),
> I tried the following but could not reproduce the oops here.
> # cryptsetup luksFormat /dev/sdb1
> # cryptsetup luksOpen /dev/sdb1 c
> # mkfs.ext3 /dev/mapper/c
> <mount it and do some I/O>
I put in the patch again and it doesn't oops anymore, so sorry for
the false alarm. I did got the oops I pasted several times before
that though, I'll keep an eye on it and try to gather more information
in case it happens again.
next prev parent reply other threads:[~2007-07-18 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 20:58 [2.6.23 PATCH 07/18] dm io: fix panic on large request Alasdair G Kergon
2007-07-17 13:16 ` Patrick McHardy
2007-07-17 16:39 ` Jun'ichi Nomura
2007-07-17 17:50 ` Patrick McHardy
2007-07-17 22:20 ` Jun'ichi Nomura
2007-07-18 10:08 ` Patrick McHardy [this message]
2007-07-18 15:23 ` Chuck Ebbert
2007-07-20 15:07 ` Milan Broz
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=469DE6B0.60807@trash.net \
--to=kaber@trash.net \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox