From: Jens Axboe <axboe@suse.de>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] More loop/BIO breakage (ll_rw_blk.c:1359)
Date: Mon, 7 Jan 2002 08:48:35 +0100 [thread overview]
Message-ID: <20020107084835.E1755@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201070828180.18265-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.33.0201070828180.18265-100000@netfinity.realnet.co.sz>
On Mon, Jan 07 2002, Zwane Mwaikambo wrote:
> Hi Jens,
> Oops reproducible by doing a "mount /dev/fd0 /floppy -o loop".
> Decoded oops at the end.
>
> loop.c
> static inline void loop_handle_bio(struct loop_device *lo, struct bio
> *bio)
> {
> <snip>
> } else {
> struct bio *rbh = bio->bi_private;
>
> ret = do_bio_blockbacked(lo, bio, rbh);
> bio_endio(rbh, !ret, bio_sectors(bio)); <== [1]
> loop_put_buffer(bio);
> }
> }
Ah excellent, nice work. Applied.
--
Jens Axboe
prev parent reply other threads:[~2002-01-07 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 6:31 [PATCH] More loop/BIO breakage (ll_rw_blk.c:1359) Zwane Mwaikambo
2002-01-07 7:48 ` Jens Axboe [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=20020107084835.E1755@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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