From: Milan Broz <mbroz@redhat.com>
To: Luzipher McLeod <luziphermcleod@yahoo.ie>
Cc: dm-crypt@saout.de, Mandeep Singh Baines <msb@chromium.org>
Subject: Re: [dm-crypt] Kernel BUG (fs/bio.c:1499) when copying more files to an encrypted device
Date: Wed, 25 Jan 2012 10:08:44 +0100 [thread overview]
Message-ID: <4F1FC69C.2090708@redhat.com> (raw)
In-Reply-To: <1327478794.47118.YahooMailClassic@web24104.mail.ird.yahoo.com>
On 01/25/2012 09:06 AM, Luzipher McLeod wrote:
> Hi Mandeep,
>
> Thanks fpr your quick answer. So, what can be done about this ?
> Should I try to apply that patch you linked to ? (but I guess a patch
> from 2007 won't apply cleanly ...)
bio_split is called from linear_make_request, which is MD raid code.
(MD linear is very rarely used IMHO, device-mapper & LVM usually works
better in this situation - can you try to reproduce it using DM?)
Anyway, seems like and MD bug, please forward it to md list
linux-raid@vger.kernel.org
(please cc me, if it uncovers some bug in dmcrypt, I'll fix it)
Milan
p.s.
> After talking to the btrfs devs on freenode (as btrfs is the most
> experimental thing in the stack, they came to the conclusion
> that it's most probably the crypto layer.
They are repeating this for years every time they see dmcrypt in stack despite
they are not able to provide reliable reproducer. We have no such report
for ext3, ext4, xfs or any other fs.
next prev parent reply other threads:[~2012-01-25 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 23:45 [dm-crypt] Kernel BUG (fs/bio.c:1499) when copying more files to an encrypted device Luzipher McLeod
2012-01-25 2:14 ` Mandeep Singh Baines
2012-01-25 8:06 ` Luzipher McLeod
2012-01-25 9:08 ` Milan Broz [this message]
2012-01-25 18:20 ` Mandeep Singh Baines
2012-01-25 23:46 ` Mandeep Singh Baines
2012-01-25 23:46 ` Mandeep Singh Baines
2012-01-30 0:46 ` Luzipher McLeod
2012-01-30 0:46 ` Luzipher McLeod
2012-01-31 23:26 ` [dm-crypt] " Luzipher McLeod
2012-01-31 23:26 ` Luzipher McLeod
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=4F1FC69C.2090708@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=luziphermcleod@yahoo.ie \
--cc=msb@chromium.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 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.