From: Andrew Morton <akpm@linux-foundation.org>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: [PATCH] check bh->b_blocknr only if BH_Mapped is set
Date: Tue, 10 Feb 2009 12:46:40 -0800 [thread overview]
Message-ID: <20090210124640.81d25a27.akpm@linux-foundation.org> (raw)
In-Reply-To: <200902091748.12545.knikanth@suse.de>
On Mon, 9 Feb 2009 17:48:11 +0530
Nikanth Karthikesan <knikanth@suse.de> wrote:
> check bh->b_blocknr only if BH_Mapped is set
Why?
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 665d446..782c365 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -344,13 +344,13 @@ __find_get_block_slow(struct block_device *bdev,
> sector_t block)
> head = page_buffers(page);
> bh = head;
> do {
> - if (bh->b_blocknr == block) {
> + if (!buffer_mapped(bh))
> + all_mapped = 0;
> + else if (bh->b_blocknr == block) {
> ret = bh;
> get_bh(bh);
> goto out_unlock;
> }
> - if (!buffer_mapped(bh))
> - all_mapped = 0;
> bh = bh->b_this_page;
> } while (bh != head);
Does this fix some user-visible misbehaviour? If so, what was that
behaviour?
Please write good changelogs. This is not some pointless book-keeping
exercise. People will make decisions about which kernel versions
patches should be merged into, and they will want to know if a
particular patch addresses a particular problem which they are
experiencing. For this, they need information.
Thanks.
next prev parent reply other threads:[~2009-02-10 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 12:18 [PATCH] check bh->b_blocknr only if BH_Mapped is set Nikanth Karthikesan
2009-02-10 20:46 ` Andrew Morton [this message]
2009-02-11 6:01 ` Nikanth Karthikesan
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=20090210124640.81d25a27.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--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