public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, Jan Kara <jack@suse.com>
Subject: Re: [PATCH] xfs: Fix file type directory corruption for btree directories
Date: Mon, 24 Aug 2015 11:26:37 +0200	[thread overview]
Message-ID: <20150824092637.GB2936@quack.suse.cz> (raw)
In-Reply-To: <20150821231154.GR3902@dastard>

On Sat 22-08-15 09:11:54, Dave Chinner wrote:
> On Fri, Aug 21, 2015 at 07:55:22PM +0200, Jan Kara wrote:
> > Users have occasionally reported that file type for some directory
> > entries is wrong. This mostly happened after updating libraries some
> > libraries. After some debugging the problem was traced down to
> > xfs_dir2_node_replace(). The function uses args->filetype as a file type
> > to store in the replaced directory entry however it also calls
> > xfs_da3_node_lookup_int() which will store file type of the current
> > directory entry in args->filetype. Thus we fail to change file type of a
> > directory entry to a proper type.
> > 
> > Fix the problem by storing new file type in a local variable before
> > calling xfs_da3_node_lookup_int().
> > 
> > Reported-by: Giacomo Comes <comes@naic.edu>
> > Signed-off-by: Jan Kara <jack@suse.com>
> 
> So this is being triggered by a rename() operation on a large
> directory? node format is the optimised form form for large dirs, so
> I suspect that's why only few people see this. Can you see if you
> can write a reproducer for it baseed on a large single directory and
> renaming two files of different types (e.g. BLKDEV over REG) to see
> if the cause is that simple?

Yes, I've tried and for a large enough directory renaming symlink over a
regular file is all that is needed to corrupt the file type in the
directory. Should I write a dedicated test for this or is there something
that already excercises directory code? I know about fsstress runs but
those would be hard to tweak to trigger this I guess.

								Honza

> > ---
> >  fs/xfs/libxfs/xfs_dir2_node.c | 8 +++++++-
> >  1 file changed, 7 insertions(+), 1 deletion(-)
> > 
> > diff --git a/fs/xfs/libxfs/xfs_dir2_node.c b/fs/xfs/libxfs/xfs_dir2_node.c
> > index 41b80d3d3877..1006710a7c92 100644
> > --- a/fs/xfs/libxfs/xfs_dir2_node.c
> > +++ b/fs/xfs/libxfs/xfs_dir2_node.c
> > @@ -2132,6 +2132,7 @@ xfs_dir2_node_replace(
> >  	int			error;		/* error return value */
> >  	int			i;		/* btree level */
> >  	xfs_ino_t		inum;		/* new inode number */
> > +	int			ftype;		/* new file type */
> >  	xfs_dir2_leaf_t		*leaf;		/* leaf structure */
> >  	xfs_dir2_leaf_entry_t	*lep;		/* leaf entry being changed */
> >  	int			rval;		/* internal return value */
> > @@ -2145,7 +2146,12 @@ xfs_dir2_node_replace(
> >  	state = xfs_da_state_alloc();
> >  	state->args = args;
> >  	state->mp = args->dp->i_mount;
> > +	/*
> > +	 * We have to save new inode number and ftype since
> > +	 * xfs_da3_node_lookup_int() is going to overwrite them
> > +	 */
> >  	inum = args->inumber;
> > +	ftype = args->filetype;
> >  	/*
> >  	 * Lookup the entry to change in the btree.
> >  	 */
> > @@ -2183,7 +2189,7 @@ xfs_dir2_node_replace(
> >  		 * Fill in the new inode number and log the entry.
> >  		 */
> >  		dep->inumber = cpu_to_be64(inum);
> > -		args->dp->d_ops->data_put_ftype(dep, args->filetype);
> > +		args->dp->d_ops->data_put_ftype(dep, ftype);
> >  		xfs_dir2_data_log_entry(args, state->extrablk.bp, dep);
> >  		rval = 0;
> >  	}
> 
> The change looks sane (i'll add whitespace around the comments when
> i commit) and I'll also add the stable cc. I would like to have a
> reproducer to test it, though ;)
> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-08-24  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 17:55 [PATCH] xfs: Fix file type directory corruption for btree directories Jan Kara
2015-08-21 18:06 ` Jan Kara
2015-08-21 23:11 ` Dave Chinner
2015-08-24  9:26   ` Jan Kara [this message]
2015-08-24 12:19     ` Dave Chinner

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=20150824092637.GB2936@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=david@fromorbit.com \
    --cc=jack@suse.com \
    --cc=xfs@oss.sgi.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