From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: ext4_dx_add_entry should dirty directory metadata with the directory inode
Date: Fri, 30 Sep 2011 12:44:17 -0700 [thread overview]
Message-ID: <20110930194417.GV12086@tux1.beaverton.ibm.com> (raw)
In-Reply-To: <ED0259FB-A818-4CAA-A72A-9164CE3769D9@dilger.ca>
On Thu, Aug 11, 2011 at 03:41:59PM -0600, Andreas Dilger wrote:
> On 2011-08-11, at 3:15 PM, Darrick J. Wong wrote:
> > ext4_dx_add_entry manipulates bh2 and frames[0].bh, which are two buffer_heads
> > that point to directory blocks assigned to the directory inode. However, the
> > function calls ext4_handle_dirty_metadata with the inode of the file that's
> > being added to the directory, not the directory inode itself. Therefore,
> > correct the code to dirty the directory buffers with the directory inode, not
> > the file inode.
>
> Interesting. For journaled filesystems this is purely cosmetic, since
> "handle" is valid and "inode" is unused in that case. For non-journal
> filesystems it actually affects the correctness, since this buffer may
> not be sync'd to disk even when the directory is marked "dirsync".
>
> You can add my:
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Hm.... any thoughts, Ted? Will this be picked up for 3.1/3.2?
--D
>
> > Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> > ---
> >
> > fs/ext4/namei.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> > index b754b77..79ddc43 100644
> > --- a/fs/ext4/namei.c
> > +++ b/fs/ext4/namei.c
> > @@ -1589,7 +1589,7 @@ static int ext4_dx_add_entry(handle_t *handle, struct dentry *dentry,
> > dxtrace(dx_show_index("node", frames[1].entries));
> > dxtrace(dx_show_index("node",
> > ((struct dx_node *) bh2->b_data)->entries));
> > - err = ext4_handle_dirty_metadata(handle, inode, bh2);
> > + err = ext4_handle_dirty_metadata(handle, dir, bh2);
> > if (err)
> > goto journal_error;
> > brelse (bh2);
> > @@ -1615,7 +1615,7 @@ static int ext4_dx_add_entry(handle_t *handle, struct dentry *dentry,
> > if (err)
> > goto journal_error;
> > }
> > - err = ext4_handle_dirty_metadata(handle, inode, frames[0].bh);
> > + err = ext4_handle_dirty_metadata(handle, dir, frames[0].bh);
> > if (err) {
> > ext4_std_error(inode->i_sb, err);
> > goto cleanup;
> > --
> > 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:[~2011-09-30 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 21:15 [PATCH] ext4: ext4_dx_add_entry should dirty directory metadata with the directory inode Darrick J. Wong
2011-08-11 21:41 ` Andreas Dilger
2011-09-30 19:44 ` Darrick J. Wong [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=20110930194417.GV12086@tux1.beaverton.ibm.com \
--to=djwong@us.ibm.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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