From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: kernel BUG at fs/xfs/xfs_message.c:113!
Date: Wed, 21 Sep 2016 06:14:53 +1000 [thread overview]
Message-ID: <20160920201453.GH340@dastard> (raw)
In-Reply-To: <20160920163304.GA8999@linux.intel.com>
On Tue, Sep 20, 2016 at 10:33:04AM -0600, Ross Zwisler wrote:
> I'm consistently able to generate this kernel BUG with both v4.7 and v4.8-rc7.
> This bug reproduces both with and without DAX.
> Here is the BUG with v4.8-rc7, passed through kasan_symbolize.py:
>
> run fstests generic/026 at 2016-09-20 10:22:58
> XFS (pmem0p2): Unmounting Filesystem
> XFS: Assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: fs/xfs/xfs_trans.c, line: 309
It overran the block allocation reservation for the transaction.
> I started hitting this issue when I started setting extsize via xfs_io on both
> my TEST and SCRATCH xfstest directories. Here's a quick snapshot of my
> xfstests setup:
>
> # parted -s -a optimal /dev/pmem0 mkpart Primary 2MiB 12GiB
> # parted -s -a optimal /dev/pmem0 mkpart Primary 12GiB 16382MiB
> # mkfs.xfs -f /dev/pmem0p1
> # mkfs.xfs -f /dev/pmem0p2
> # mount /dev/pmem0p1 /mnt/xfstests_test
> # mount /dev/pmem0p2 /mnt/xfstests_scratch
> # xfs_io -c 'extsize 2m' /mnt/xfstests_test
> # xfs_io -c 'extsize 2m' /mnt/xfstests_scratch
The test dir is the one that matters here - I can reproduce it
locally so I'll have a look.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: kernel BUG at fs/xfs/xfs_message.c:113!
Date: Wed, 21 Sep 2016 06:14:53 +1000 [thread overview]
Message-ID: <20160920201453.GH340@dastard> (raw)
In-Reply-To: <20160920163304.GA8999@linux.intel.com>
On Tue, Sep 20, 2016 at 10:33:04AM -0600, Ross Zwisler wrote:
> I'm consistently able to generate this kernel BUG with both v4.7 and v4.8-rc7.
> This bug reproduces both with and without DAX.
> Here is the BUG with v4.8-rc7, passed through kasan_symbolize.py:
>
> run fstests generic/026 at 2016-09-20 10:22:58
> XFS (pmem0p2): Unmounting Filesystem
> XFS: Assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: fs/xfs/xfs_trans.c, line: 309
It overran the block allocation reservation for the transaction.
> I started hitting this issue when I started setting extsize via xfs_io on both
> my TEST and SCRATCH xfstest directories. Here's a quick snapshot of my
> xfstests setup:
>
> # parted -s -a optimal /dev/pmem0 mkpart Primary 2MiB 12GiB
> # parted -s -a optimal /dev/pmem0 mkpart Primary 12GiB 16382MiB
> # mkfs.xfs -f /dev/pmem0p1
> # mkfs.xfs -f /dev/pmem0p2
> # mount /dev/pmem0p1 /mnt/xfstests_test
> # mount /dev/pmem0p2 /mnt/xfstests_scratch
> # xfs_io -c 'extsize 2m' /mnt/xfstests_test
> # xfs_io -c 'extsize 2m' /mnt/xfstests_scratch
The test dir is the one that matters here - I can reproduce it
locally so I'll have a look.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-09-20 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 16:33 kernel BUG at fs/xfs/xfs_message.c:113! Ross Zwisler
2016-09-20 16:33 ` Ross Zwisler
2016-09-20 20:14 ` Dave Chinner [this message]
2016-09-20 20:14 ` Dave Chinner
2016-09-20 23:06 ` Dave Chinner
2016-09-20 23:06 ` Dave Chinner
2016-09-21 15:38 ` Ross Zwisler
2016-09-21 15:38 ` Ross Zwisler
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=20160920201453.GH340@dastard \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ross.zwisler@linux.intel.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 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.