public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] ext4: remove redundant code in ext4_fill_super()
Date: Fri, 30 May 2008 13:57:27 -0700	[thread overview]
Message-ID: <1212181047.3719.10.camel@localhost.localdomain> (raw)
In-Reply-To: <483F8D31.7090505@cn.fujitsu.com>

On Fri, 2008-05-30 at 13:14 +0800, Li Zefan wrote:
> The previous sb_min_blocksize() has already set the block size.
> 
> This piece of code was introduced in commit:
> 	afc7cbca5bfd556c3e12d3acefbee5ab0cbd4670
> 	(ext4: Support large blocksize up to PAGESIZE)
> And it should be a mistake.
> 
Signed-off-by: Mingming Cao <cmm@us.ibm.com>

Added to  ext4 patch queue http://repo.or.cz/w/ext4-patch-queue.git
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
>  fs/ext4/super.c |    5 -----
>  1 files changed, 0 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 09d9359..5d07aa9 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -1843,11 +1843,6 @@ static int ext4_fill_super (struct super_block *sb, void *data, int silent)
>  		goto out_fail;
>  	}
> 
> -	if (!sb_set_blocksize(sb, blocksize)) {
> -		printk(KERN_ERR "EXT4-fs: bad blocksize %d.\n", blocksize);
> -		goto out_fail;
> -	}
> -
>  	/*
>  	 * The ext4 superblock will not be buffer aligned for other than 1kB
>  	 * block sizes.  We need to calculate the offset from buffer start.


      reply	other threads:[~2008-05-30 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30  5:14 [PATCH] ext4: remove redundant code in ext4_fill_super() Li Zefan
2008-05-30 20:57 ` Mingming Cao [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=1212181047.3719.10.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=tytso@mit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox