From: Christophe Saout <christophe@saout.de>
To: Michael Buesch <mbuesch@freenet.de>
Cc: linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: swap on dmcrypt crashes machine
Date: Thu, 27 Jan 2005 15:34:50 +0100 [thread overview]
Message-ID: <1106836490.27812.6.camel@server.cs.pocnet.net> (raw)
In-Reply-To: <200501251828.17569.mbuesch@freenet.de>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Am Dienstag, den 25.01.2005, 18:28 +0100 schrieb Michael Buesch:
> I set up swap on an encrypted dmcrypt device.
> While stressing swap usage with make -j200 in the
> kernel tree, the machine crashes:
>
> Adding 1461872k swap on /dev/mapper/swap. Priority:-2 extents:1
> ------------[ cut here ]------------
> kernel BUG at drivers/block/ll_rw_blk.c:2193!
> invalid operand: 0000 [#1]
> SMP
> Modules linked in: ipv6 ohci_hcd tuner tvaudio msp3400 bttv video_buf firmware_class btcx_risc nvidia ehci_hcd uhci_hcd usbcore intel_agp agpgart evdev
> CPU: 0
> EIP: 0060:[<c0218b8a>] Tainted: P VLI
> EFLAGS: 00210002 (2.6.10-ck4-defaultidle)
> EIP is at __blk_put_request+0x87/0x91
This seems to be this BUG:
BUG_ON(!list_empty(&req->queuelist));
in drivers/block/ll_rw_blk.c. I don't know how this could be non-empty
since scsi_end_request calls
if (blk_rq_tagged(req))
blk_queue_end_tag(q, req);
just before calling end_that_request_last inside the same spinlock.
I don't know anything about tagged request handling but I don't think
this is the fault of the dm-crypt driver, perhaps it's stressing the
queue in some unexpected way? I have no idea what's going on here.
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-27 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 17:28 Michael Buesch
2005-01-27 14:34 ` Christophe Saout [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=1106836490.27812.6.camel@server.cs.pocnet.net \
--to=christophe@saout.de \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome