From: Jens Axboe <axboe@suse.de>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix loop BIO breakage (memory corruption)
Date: Thu, 3 Jan 2002 09:48:32 +0100 [thread overview]
Message-ID: <20020103094832.E482@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201030803570.20656-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.33.0201030803570.20656-100000@netfinity.realnet.co.sz>
On Thu, Jan 03 2002, Zwane Mwaikambo wrote:
> Hi Jens,
> I've tracked down what seems to be a case of array out of bounds.
> Doing the following command "mount /dev/cdrom /cdrom -o loop" hard locks
[snip]
Thanks, good debugging. This bug has been there in 2.4 before, blush.
I've applied your patch.
> Patch tested with read/write losetup type mounts, plain file backed mounts
> and block backed mounts (these fail in ll_rw_blk:1365 BUG check now)
Oh? Care to look into this?
--
Jens Axboe
next prev parent reply other threads:[~2002-01-03 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 6:06 [PATCH] Fix loop BIO breakage (memory corruption) Zwane Mwaikambo
2002-01-03 8:48 ` Jens Axboe [this message]
2002-01-03 9:15 ` Zwane Mwaikambo
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=20020103094832.E482@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zwane@linux.realnet.co.sz \
/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