public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Salah Triki <salah.triki@gmail.com>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	viro@zeniv.linux.org.uk, salah.triki@acm.org
Subject: Re: [PATCH 2/4] befs: add check for ag_shift in superblock
Date: Thu, 11 Aug 2016 15:58:59 +0100	[thread overview]
Message-ID: <20160811145859.GA4294@pc> (raw)
In-Reply-To: <1470780086-11594-2-git-send-email-luisbg@osg.samsung.com>

On Tue, Aug 09, 2016 at 11:01:24PM +0100, Luis de Bethencourt wrote:
> ag_shift and blocks_per_ag contain the same information in different ways,
> same as block_shift and block_size do. It is worth checking this two are
> consistent, but since blocks_per_ag isn't documented as mandatory to use
> some implementations of befs don't enforce this, so making it non-fatal if
> they don't match and just having it as a warning.
> 
> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
> ---
>  fs/befs/super.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/fs/befs/super.c b/fs/befs/super.c
> index dc13df8..c36745d 100644
> --- a/fs/befs/super.c
> +++ b/fs/befs/super.c
> @@ -103,6 +103,13 @@ befs_check_sb(struct super_block *sb)
>  		return BEFS_ERR;
>  	}
>  
> +
> +	/* ag_shift also encodes the same information as blocks_per_ag in a
> +	 * different way, non-fatal consistency check
> +	 */
> +	if ((1 << befs_sb->ag_shift) != befs_sb->blocks_per_ag)
> +		befs_error(sb, "ag_shift disagrees with blocks_per_ag.");
> +
>  	if (befs_sb->log_start != befs_sb->log_end || befs_sb->flags == BEFS_DIRTY) {
>  		befs_error(sb, "Filesystem not clean! There are blocks in the "
>  			   "journal. You must boot into BeOS and mount this volume "
> -- 
> 2.5.1
> 

Signed-off-by: Salah Triki <salah.triki@gmail.com>

Thanx :)
Salah

  reply	other threads:[~2016-08-11 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 22:01 [PATCH 1/4] befs: dump inode_size superblock information Luis de Bethencourt
2016-08-09 22:01 ` [PATCH 2/4] befs: add check for ag_shift in superblock Luis de Bethencourt
2016-08-11 14:58   ` Salah Triki [this message]
2016-08-09 22:01 ` [PATCH 3/4] befs: fix comment style Luis de Bethencourt
2016-08-10 21:42   ` Salah Triki
2016-08-09 22:01 ` [PATCH 4/4] befs: fix style issues in super.c Luis de Bethencourt
2016-08-10 21:44   ` Salah Triki
2016-08-10 21:41 ` [PATCH 1/4] befs: dump inode_size superblock information Salah Triki
2016-08-11 10:03   ` Luis de Bethencourt
2016-08-11 14:09     ` Salah Triki

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=20160811145859.GA4294@pc \
    --to=salah.triki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    --cc=salah.triki@acm.org \
    --cc=viro@zeniv.linux.org.uk \
    /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