All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] xfstests: xfs discontiguous multi-block buffer logging test
Date: Thu, 16 Jun 2016 07:45:25 -0400	[thread overview]
Message-ID: <20160616114525.GA8342@bfoster.bfoster> (raw)
In-Reply-To: <20160616011349.GM12670@dastard>

On Thu, Jun 16, 2016 at 11:13:49AM +1000, Dave Chinner wrote:
> On Thu, Jun 02, 2016 at 09:10:01AM -0400, Brian Foster wrote:
> > XFS had a bug in the multi-block buffer logging code that caused a NULL
> > lv panic at log push time due to invalid regions being set in the buffer
> > log format bitmap. This was demonstrated by modifying a multi-block
> > directory buffer in a manner that only logs regions beyond the first
> > FSB-sized mapping of the buffer.
> > 
> > To recreate these conditions, this test fragments free space and
> > populates several directories with enough entries to require
> > discontiguous multi-block buffers. To recreate the problem, we remove
> > entries from the tail end of the directory and fsync to flush the log.
> > 
> > Note that this test causes a panic on kernels affected by the bug. As
> > such, it is included in the 'dangerous' group. The bug is resolved by
> > kernel commit a3916e528b91 ("xfs: fix broken multi-fsb buffer logging").
> > 
> > Signed-off-by: Brian Foster <bfoster@redhat.com>
> .....
> > +# Create a small fs with a large directory block size. We want to fill up the fs
> > +# quickly and then create multi-fsb dirblocks over fragmented free space.
> > +_scratch_mkfs_xfs -d size=20m -n size=64k >> $seqres.full 2>&1
> > +_scratch_mount
> > +
> > +# Fill a source directory with many largish-named files. 1k uuid-named entries
> > +# sufficiently populates a 64k directory block.
> > +mkdir $SCRATCH_MNT/src
> > +for i in $(seq 0 1023); do
> > +	touch $SCRATCH_MNT/src/`uuidgen`
> > +done
> 
> What's 'uuidgen'? Not installed on my test systems, so this needs
> a requires check, I think....
> 
> Hmmm - looks like a separate package is needed on debian systems:
> uuid-runtime. Can you send a followup patch that adds the necesary
> checks to this test and added the above package to the iniitial list
> in the README file (for ubunutu, I know, but the package name will
> be the same).
> 

Eryu pointed this on on v1 of the test but I didn't think it necessary
as it's part of a standard package on fedora. I guess that's not true
for other distros. I'll post something to fix it up...

Brian

> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-06-16 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 13:10 [PATCH v2] xfstests: xfs discontiguous multi-block buffer logging test Brian Foster
2016-06-03  3:31 ` Eryu Guan
2016-06-16  1:13 ` Dave Chinner
2016-06-16 11:45   ` Brian Foster [this message]
2016-06-16 15:10     ` Eric Sandeen
2016-06-20 22:48       ` 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=20160616114525.GA8342@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.