From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: mh@nadir.org, Linux Kernel list <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: oops w/ 2.6.2-mm1 on ppc32
Date: Sun, 15 Feb 2004 20:49:21 +1100 [thread overview]
Message-ID: <1076838561.6949.42.camel@gaston> (raw)
In-Reply-To: <20040215001019.33e4089b.akpm@osdl.org>
> Note that isofs_fill_super() calls sb_bread() before setting the blocksize.
> For this it is relying on blockdev.bd_block_size being set up
> appropriately.
>
> Which all tends to imply that the underlying queue's ->hardsect_size is
> very wrong.
>
> The code which is responsible for setting up the queue's hardsect_size
> appears to live in cdrom_read_toc()
>
.../...
I have to double check, but that sounds a bit like some oops report
I got with HFS/HFS+ on CD-ROMs... I'll check my archives tomorrow
Ben.
next prev parent reply other threads:[~2004-02-15 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 7:41 oops w/ 2.6.2-mm1 on ppc32 Marc Heckmann
2004-02-15 7:49 ` Benjamin Herrenschmidt
2004-02-15 8:10 ` Andrew Morton
2004-02-15 9:42 ` Jens Axboe
2004-02-15 9:49 ` Benjamin Herrenschmidt [this message]
2004-02-15 8:24 ` Marc Heckmann
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=1076838561.6949.42.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mh@nadir.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox