From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, jeffm@suse.com,
torvalds@osdl.org
Subject: Re: [PATCH] fs: remove s_old_blocksize from struct super_block
Date: Sat, 03 Dec 2005 13:34:04 +0200 [thread overview]
Message-ID: <1133609645.7989.3.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0512031058350.11664@hermes-1.csi.cam.ac.uk>
Hi Anton,
On Fri, 2 Dec 2005, Pekka Enberg wrote:
> > The s_old_blocksize field of struct super_block is only used as a temporary
> > variable in get_sb_bdev(). This patch changes the function to use a local
> > variable instead so we can kill the field from struct super_block.
On Sat, 2005-12-03 at 11:02 +0000, Anton Altaparmakov wrote:
> s_old_blocksize used to be used to restore the blocksize after the
> filesystem had failed to mount or had unmounted. Not restoring this leads
> to all sorts of problems since the blocksize may be set for example to 4k
> but some userspace app may need it to be set to 1k or whatever. There
> used to be applications that failed which is why s_old_blocksize was
> introduced and it used to restore the blocksize.
>
> I have no idea why/when the restoring has been removed but chances are the
> removal was wrong. Now every file system will need to restore the
> blocksize itself (as it used to be before s_old_blocksize and blocksize
> restoral was introduced). Except whoever removed the restoration failed
> to fix up all file systems. )-:
It was removed in this commit, I think:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commit;h=294c42046966e927ef86c0d4ce71cff32d9b458c
Pekka
next prev parent reply other threads:[~2005-12-03 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 21:20 [PATCH] fs: remove s_old_blocksize from struct super_block Pekka Enberg
2005-12-02 21:44 ` Pekka Enberg
2005-12-03 11:02 ` Anton Altaparmakov
2005-12-03 11:34 ` Pekka Enberg [this message]
2005-12-03 14:34 ` Anton Altaparmakov
2005-12-03 17:42 ` Jeff Mahoney
2005-12-03 18:52 ` Linus Torvalds
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=1133609645.7989.3.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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