From: Theodore Tso <tytso@mit.edu>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] EXT4: Avoid double dirtying of super block in ext4_put_super()
Date: Mon, 6 Oct 2008 19:39:49 -0400 [thread overview]
Message-ID: <20081006233949.GB9337@mit.edu> (raw)
In-Reply-To: <20081006212118.GA382@basil.nowhere.org>
On Mon, Oct 06, 2008 at 11:21:18PM +0200, Andi Kleen wrote:
> EXT4: Avoid double dirtying of super block in ext4_put_super()
>
> While reading code I noticed that ext4_put_super() dirties the
> superblock bh twice. It is always done in ext4_commit_super()
> too. Remove the redundant dirty operation.
>
> Should be a nop semantically.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
As it turns out, I had taken out the mark_buffer_dirty as superfluous
in the following patch:
ext4/jbd2: Avoid WARN() messages when failing to write to the superblock
(This was Arjan's favorite ext3/ext4 top-ten kerneloops.org bug).
However I didn't kill the BUFFER_TRACE(sbi->s_sbh, "marking dirty");
line, which should have been deleted too. I'll take out the change
from my patch since it's really unrelated to fixing the kerneloops.org
WARN'ing, and take your patch and it include it for submission to
Linus in the ext3 tree.
Thanks,
- Ted
prev parent reply other threads:[~2008-10-06 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 21:21 [PATCH] EXT4: Avoid double dirtying of super block in ext4_put_super() Andi Kleen
2008-10-06 23:39 ` Theodore Tso [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=20081006233949.GB9337@mit.edu \
--to=tytso@mit.edu \
--cc=andi@firstfloor.org \
--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