From: Jan Kara <jack@suse.cz>
To: Eryu Guan <guaneryu@gmail.com>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext3: call ext3_mark_recovery_complete() when recovery is really needed
Date: Thu, 3 Nov 2011 02:35:51 +0100 [thread overview]
Message-ID: <20111103013551.GA13266@quack.suse.cz> (raw)
In-Reply-To: <CA+dCu88f-5FVBHk6-jv0X_PSJ=aS=+uRVJemS3-=p_+5FiCfmA@mail.gmail.com>
On Wed 02-11-11 22:04:54, Eryu Guan wrote:
> On Wed, Nov 2, 2011 at 6:43 AM, Jan Kara <jack@suse.cz> wrote:
> > On Tue 01-11-11 10:06:19, Eryu Guan wrote:
> >> Call ext3_mark_recovery_complete() in ext3_fill_super() only if
> >> needs_recovery is non-zero.
> >>
> >> Besides that, print out "recovery complete" message after calling
> >> ext3_mark_recovery_complete().
> > OK, I don't see a problem in this patch. But is there some benefit in it?
> > I'm slightly nervous it could change something subtle...
>
> I think current code may confuse people. The variable 'needs_recovery' in
> ext3_fill_super() only be used in this 'if' switch, but all the 'if'
> does is printing
> out a log message and no matter what value 'needs_recovery' is,
> ext3_mark_recovery_complete() is always being called.
>
> This change makes the logic more clear and of course reduce a little overhead
> when mounting clean fs.
>
> This change also consists with ext4 counter part
> 3733 if (needs_recovery) {
> 3734 ext4_msg(sb, KERN_INFO, "recovery complete");
> 3735 ext4_mark_recovery_complete(sb, es);
> 3736 }
OK, consistency with ext4 makes sense. I'll take the patch. Thanks.
Honza
> >> Cc: Jan Kara <jack@suse.cz>
> >> Signed-off-by: Eryu Guan <guaneryu@gmail.com>
> >> ---
> >> fs/ext3/super.c | 5 +++--
> >> 1 files changed, 3 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/fs/ext3/super.c b/fs/ext3/super.c
> >> index 7beb69a..2681e0d 100644
> >> --- a/fs/ext3/super.c
> >> +++ b/fs/ext3/super.c
> >> @@ -2060,9 +2060,10 @@ static int ext3_fill_super (struct super_block *sb, void *data, int silent)
> >> EXT3_SB(sb)->s_mount_state |= EXT3_ORPHAN_FS;
> >> ext3_orphan_cleanup(sb, es);
> >> EXT3_SB(sb)->s_mount_state &= ~EXT3_ORPHAN_FS;
> >> - if (needs_recovery)
> >> + if (needs_recovery) {
> >> + ext3_mark_recovery_complete(sb, es);
> >> ext3_msg(sb, KERN_INFO, "recovery complete");
> >> - ext3_mark_recovery_complete(sb, es);
> >> + }
> >> ext3_msg(sb, KERN_INFO, "mounted filesystem with %s data mode",
> >> test_opt(sb,DATA_FLAGS) == EXT3_MOUNT_JOURNAL_DATA ? "journal":
> >> test_opt(sb,DATA_FLAGS) == EXT3_MOUNT_ORDERED_DATA ? "ordered":
> >> --
> >> 1.7.7.1
> >>
> > --
> > Jan Kara <jack@suse.cz>
> > SUSE Labs, CR
> >
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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:[~2011-11-03 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 2:06 [PATCH] ext3: call ext3_mark_recovery_complete() when recovery is really needed Eryu Guan
2011-11-01 22:43 ` Jan Kara
2011-11-02 14:04 ` Eryu Guan
2011-11-03 1:35 ` 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=20111103013551.GA13266@quack.suse.cz \
--to=jack@suse.cz \
--cc=guaneryu@gmail.com \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).