From: Jens Axboe <jens.axboe@oracle.com>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
bhalevy@panasas.com, Andrew Morton <akpm@linux-foundation.org>,
fujita.tomonori@lab.ntt.co.jp, michaelc@cs.wisc.edu
Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
Date: Fri, 18 May 2007 19:03:24 +0200 [thread overview]
Message-ID: <20070518170323.GI23798@kernel.dk> (raw)
In-Reply-To: <1179504198.29302.12.camel@dyn9047017100.beaverton.ibm.com>
On Fri, May 18 2007, Badari Pulavarty wrote:
> On Fri, 2007-05-18 at 09:33 +0200, Jens Axboe wrote:
> > On Thu, May 17 2007, Badari Pulavarty wrote:
> > > On Thu, 2007-05-17 at 08:27 +0200, Jens Axboe wrote:
> > > ..
> > > > > >
> > > > > > Ah ok, you need the updated patch series for ppc64 support. Builds fine
> > > > > > here on ppc64. See the #sglist branch of the block repo:
> > > > > >
> > > > > > git://git.kernel.dk/data/git/linux-2.6-block.git
> > > > > >
> > > > > > I can mail you an updated patch, if you want.
> > > > >
> > > > >
> > > > > Here is the whole panic stack..
> > > >
> > > > Thanks will fix that up, the IDE part is totally untested. Can you try
> > > > and backout this patch and see if it boots?
> > >
> > > Yes. It boots fine with following backed out.
> > >
> > > Looking at the code ide_probe.c: hwif_init() is doing
> > >
> > > hwif->sg_table = kmalloc(sizeof(struct scatterlist)*hwif->sg_max_nents,
> > > GFP_KERNEL);
> > >
> > > blk_rq_map_sg() is looking for the chaining info and going over end of the
> > > allocation.
> >
> > Hmm, looks ok, I'm guessing it's just missing a memset (or just turn it
> > into a kzalloc())?
> >
>
> Even with backing out all the ide changes, I get this on boot
> once in a while.
Yep, I think the ide changes are fine as such, the problem is the
missing memset/kzalloc. Can you try that?
--
Jens Axboe
next prev parent reply other threads:[~2007-05-18 17:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 13:51 [PATCH] Chaining sg lists for big IO commands v5 Jens Axboe
2007-05-15 17:15 ` Badari Pulavarty
2007-05-15 17:20 ` Jens Axboe
2007-05-15 17:43 ` Badari Pulavarty
2007-05-15 17:50 ` Jens Axboe
2007-05-15 18:23 ` Jens Axboe
2007-05-16 20:58 ` Badari Pulavarty
2007-05-16 21:01 ` Badari Pulavarty
2007-05-17 6:27 ` Jens Axboe
2007-05-17 15:11 ` Badari Pulavarty
2007-05-18 7:33 ` Jens Axboe
2007-05-18 16:03 ` Badari Pulavarty
2007-05-18 17:03 ` Jens Axboe [this message]
2007-05-18 17:50 ` Badari Pulavarty
2007-05-17 15:15 ` Badari Pulavarty
2007-05-18 7:35 ` Jens Axboe
2007-05-18 17:51 ` Badari Pulavarty
2007-05-21 6:14 ` Jens Axboe
2007-05-21 6:35 ` Jens Axboe
2007-05-21 7:14 ` Benny Halevy
2007-05-22 22:15 ` Badari Pulavarty
2007-05-24 9:34 ` Jens Axboe
2007-05-24 9:43 ` FUJITA Tomonori
2007-05-24 10:00 ` Jens Axboe
2007-05-24 12:05 ` Jens Axboe
2007-05-24 12:44 ` FUJITA Tomonori
2007-05-24 12:49 ` Jens Axboe
2007-05-24 15:39 ` James Bottomley
2007-05-24 16:01 ` FUJITA Tomonori
2007-05-24 16:08 ` James Bottomley
2007-05-24 12:05 ` Jens Axboe
2007-05-24 15:25 ` Badari Pulavarty
2007-05-25 6:49 ` Jens Axboe
2007-05-22 15:35 ` Badari Pulavarty
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=20070518170323.GI23798@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=pbadari@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).