From: Jens Axboe <axboe@suse.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Srihari Vijayaraghavan <harisri@bigpond.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: 2.5.49: kernel BUG at drivers/block/ll_rw_blk.c:1950!
Date: Mon, 2 Dec 2002 09:24:16 +0100 [thread overview]
Message-ID: <20021202082416.GT16942@suse.de> (raw)
In-Reply-To: <15850.40983.669484.665564@notabene.cse.unsw.edu.au>
On Mon, Dec 02 2002, Neil Brown wrote:
> On Wednesday November 27, axboe@suse.de wrote:
> > On Wed, Nov 27 2002, Srihari Vijayaraghavan wrote:
> > > Hello Neil,
> > >
> > > On Wednesday 27 November 2002 07:13, Neil Brown wrote:
> > > > Srihari, could you possibly try with the following patch please to see
> > > > if it gives more useful information.
> > >
> > > No worries. That did the trick.
> > >
> > > The following message appears just before the first oops:
> > > Nov 27 18:56:32 localhost kernel: bio_add_page: want to add 4096 at 17658 but
> > > only allowed 3072 - prepare to oops...
> >
> > Neil, this is the problem. Currently a driver _must_ be able to accept a
> > page worth of data at any location...
>
> so raid0 (and linear) need to be able to split a bio .... I think
> we've been here before. Did you say you have plans for some generic
> helper code that could do this?
I'm afraid so... I'll come up with a splitter helper today/tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2002-12-02 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 11:03 2.5.49: kernel BUG at drivers/block/ll_rw_blk.c:1950! Srihari Vijayaraghavan
2002-11-26 19:56 ` Andrew Morton
2002-11-26 20:13 ` Neil Brown
2002-11-27 8:12 ` Srihari Vijayaraghavan
2002-11-27 8:29 ` Jens Axboe
2002-11-27 8:37 ` Andrew Morton
2002-12-01 23:49 ` Neil Brown
2002-12-02 8:24 ` Jens Axboe [this message]
2002-11-26 20:22 ` Arjan van de Ven
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=20021202082416.GT16942@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=arjanv@redhat.com \
--cc=harisri@bigpond.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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