From: Andrew Morton <akpm@digeo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Alexander Viro <viro@math.psu.edu>,
"Adam J. Richter" <adam@yggdrasil.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i_blkbits inconsistency
Date: Fri, 25 Oct 2002 14:38:25 -0700 [thread overview]
Message-ID: <3DB9B9D1.D049C730@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210252158020.1213-100000@localhost.localdomain
Hugh Dickins wrote:
>
> Fix premature -EIO from blkdev_get_block: bdget initialize bd_block_size
> consistent with bd_inode->i_blkbits (assigned by new_inode). Otherwise,
> subsequent set_blocksize can find bd_block_size doesn't need updating,
> and skip updating i_blkbits, leaving them inconsistent.
>
> --- 2.5.44/fs/block_dev.c Sat Oct 19 07:14:45 2002
> +++ linux/fs/block_dev.c Fri Oct 25 21:30:41 2002
> @@ -310,6 +310,7 @@
> new_bdev->bd_queue = NULL;
> new_bdev->bd_contains = NULL;
> new_bdev->bd_inode = inode;
> + new_bdev->bd_block_size = (1 << inode->i_blkbits);
> new_bdev->bd_part_count = 0;
> new_bdev->bd_invalidated = 0;
> inode->i_mode = S_IFBLK;
Thanks, sleuth. Wondering if we can we remove bd_block_size
and simply use (1 << bdev->bd_inode->i_blkbits) everywhere?
prev parent reply other threads:[~2002-10-25 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 21:01 [PATCH] i_blkbits inconsistency Hugh Dickins
2002-10-25 21:38 ` Andrew Morton [this message]
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=3DB9B9D1.D049C730@digeo.com \
--to=akpm@digeo.com \
--cc=adam@yggdrasil.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.