From: Jens Axboe <axboe@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE: Do not call bh_phys() on buffers with invalid b_page.
Date: Wed, 29 Jan 2003 16:38:20 +0100 [thread overview]
Message-ID: <20030129153820.GF31566@suse.de> (raw)
In-Reply-To: <1043853975.1668.74.camel@zion.wanadoo.fr>
On Wed, Jan 29 2003, Benjamin Herrenschmidt wrote:
> On Wed, 2003-01-29 at 16:22, Jens Axboe wrote:
>
> > Ehm no, if b_data is < PAGE_SIZE, it's probably an offset and not a
> > valid address. So it should be exactly where it is -- for b_page, it's
> > _not_ buggy for b_data to be < PAGE_SIZE. That's expected. Submitter
> > would have to be buggy for it to trigger, though, so you can just remove
> > it if you want.
>
> Ah, I see what you wanted to check now :) Ok, I won't remove it, though
> it would still make sense to extend the test to PAGE_OFFSET I beleive,
> any b_data < PAGE_OFFSET is wrong.
No, any b_data < PAGE_OFFSET is not wrong, that's the point. For highmem
b_page, b_data will be the offset into the page. So it could be 2048,
for instance.
The test is meant to catch an invalid buffer_head, where b_page is not
set but b_data isn't valid either. So to make it complete, you could do:
if (bh->b_page) {
...
if (bh->b_data >= PAGE_SIZE)
BUG();
} else {
...
if (bh->b_data < PAGE_SIZE)
BUG();
if (bh->b_data < PAGE_OFFSET)
BUG();
}
as they are two different bugs.
> Anyway, let's leave 2.4 as it is now.
:-)
--
Jens Axboe
next prev parent reply other threads:[~2003-01-29 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 14:57 [PATCH] IDE: Do not call bh_phys() on buffers with invalid b_page Benjamin Herrenschmidt
2003-01-29 15:00 ` Jens Axboe
2003-01-29 15:20 ` Benjamin Herrenschmidt
2003-01-29 15:22 ` Jens Axboe
2003-01-29 15:26 ` Benjamin Herrenschmidt
2003-01-29 15:38 ` Jens Axboe [this message]
2003-01-29 15:44 ` Benjamin Herrenschmidt
2003-01-29 15:47 ` Jens Axboe
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=20030129153820.GF31566@suse.de \
--to=axboe@suse.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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