From: Jan Kara <jack@suse.cz>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext3: force ro mount if ext3_setup_super() fails
Date: Tue, 29 May 2012 16:09:16 +0200 [thread overview]
Message-ID: <20120529140916.GD23991@quack.suse.cz> (raw)
In-Reply-To: <49CDEB80-418A-492C-B3F1-8E2A46DA9E29@dilger.ca>
On Thu 24-05-12 11:41:57, Andreas Dilger wrote:
> On 2012-05-24, at 11:00 AM, Eric Sandeen wrote:
> > If ext3_setup_super() fails i.e. due to a too-high revision,
> > the error is logged in dmesg but the fs is not mounted RO as
> > indicated.
> >
> > Tested by:
> >
> > # mkfs.ext3 -r 4 /dev/sdb6
> > # mount /dev/sdb6 /mnt/test
> > # dmesg | grep "too high"
> > [164152.114551] EXT3-fs (sdb6): error: revision level too high, forcing read-only mode
> > # grep sdb6 /proc/mounts
> > /dev/sdb6 /mnt/test2 ext3 rw,seclabel,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0
> > ^^
> >
> > Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>
> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Thanks! Merged to my tree.
Honza
> > ---
> >
> > diff --git a/fs/ext3/super.c b/fs/ext3/super.c
> > index cf0b592..fef7af2 100644
> > --- a/fs/ext3/super.c
> > +++ b/fs/ext3/super.c
> > @@ -2043,7 +2043,8 @@ static int ext3_fill_super (struct super_block *sb, void *data, int silent)
> > goto failed_mount3;
> > }
> >
> > - ext3_setup_super (sb, es, sb->s_flags & MS_RDONLY);
> > + if (ext3_setup_super(sb, es, sb->s_flags & MS_RDONLY))
> > + sb->s_flags |= MS_RDONLY;
>
> I was wondering if this should be:
>
> sb->s_flags |= ext3_setup_super(...)
>
> but that might be over-thinking things.
>
> > EXT3_SB(sb)->s_mount_state |= EXT3_ORPHAN_FS;
> > ext3_orphan_cleanup(sb, es);
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> Cheers, Andreas
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-05-29 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 17:00 [PATCH] ext3: force ro mount if ext3_setup_super() fails Eric Sandeen
2012-05-24 17:41 ` Andreas Dilger
2012-05-29 14:09 ` Jan Kara [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=20120529140916.GD23991@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).