From: Eric Biggers <ebiggers3@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: WARNING at fs/btrfs/inode.c:9261 btrfs_destroy_inode()
Date: Tue, 10 May 2016 18:19:20 -0500 [thread overview]
Message-ID: <20160510231920.GA938@zzz> (raw)
Hello,
The following warning has been triggering for me since about v4.6-rc3:
WARN_ON(BTRFS_I(inode)->csum_bytes);
On one machine the warning has occurred 657 times since v4.6-rc5. On another it
has occurred 3 times since v4.6-rc3. Both are now on v4.6-rc7, where I have
still observed the warning. The warnings occur in groups, and do_unlinkat() and
evict() are always in the call stack.
Is this a known issue? Here is the first occurrence:
Apr 17 10:31:19 zzz kernel: ------------[ cut here ]------------
Apr 17 10:31:19 zzz kernel: WARNING: CPU: 0 PID: 4092 at fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x23c/0x2b0
Apr 17 10:31:19 zzz kernel: Modules linked in: fuse vhost_net vhost tun bridge stp llc ccm iptable_filter iptable_nat nf_conntrack_ipv4
Apr 17 10:31:19 zzz kernel: CPU: 0 PID: 4092 Comm: rm Tainted: G W 4.6.0-rc3 #178
Apr 17 10:31:19 zzz kernel: Hardware name: Dell Inc. Inspiron 15-7568/0M5YMV, BIOS 01.00.00 08/07/2015
Apr 17 10:31:19 zzz kernel: 0000000000000286 0000000031dfd09a ffff8801b9277dc0 ffffffff813320d8
Apr 17 10:31:19 zzz kernel: 0000000000000000 0000000000000000 ffff8801b9277e00 ffffffff81074221
Apr 17 10:31:19 zzz kernel: 0000242d85cec000 ffff88019408c9a8 ffff88019408c9a8 ffff880085cec000
Apr 17 10:31:19 zzz kernel: Call Trace:
Apr 17 10:31:19 zzz kernel: [<ffffffff813320d8>] dump_stack+0x4d/0x65
Apr 17 10:31:19 zzz kernel: [<ffffffff81074221>] __warn+0xc1/0xe0
Apr 17 10:31:19 zzz kernel: [<ffffffff81074348>] warn_slowpath_null+0x18/0x20
Apr 17 10:31:19 zzz kernel: [<ffffffff8126e77c>] btrfs_destroy_inode+0x23c/0x2b0
Apr 17 10:31:19 zzz kernel: [<ffffffff81185296>] destroy_inode+0x36/0x60
Apr 17 10:31:19 zzz kernel: [<ffffffff811853e4>] evict+0x124/0x180
Apr 17 10:31:19 zzz kernel: [<ffffffff81185b68>] iput+0x148/0x1d0
Apr 17 10:31:19 zzz kernel: [<ffffffff8117b884>] do_unlinkat+0x194/0x2b0
Apr 17 10:31:19 zzz kernel: [<ffffffff8117c0e6>] SyS_unlinkat+0x16/0x30
Apr 17 10:31:19 zzz kernel: [<ffffffff817031db>] entry_SYSCALL_64_fastpath+0x13/0x8f
Apr 17 10:31:19 zzz kernel: ---[ end trace 87f6a0e10f4df484 ]---
next reply other threads:[~2016-05-10 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 23:19 Eric Biggers [this message]
2016-05-10 23:57 ` WARNING at fs/btrfs/inode.c:9261 btrfs_destroy_inode() Chris Mason
2016-05-11 18:25 ` Adam Borowski
2016-05-11 18:29 ` [PATCH for 4.6] btrfs: disable a spurious WARN_ON in btrfs_destroy_inode Adam Borowski
2016-05-11 20:17 ` Josef Bacik
2016-05-14 0:56 ` WARNING at fs/btrfs/inode.c:9261 btrfs_destroy_inode() Chris Mason
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=20160510231920.GA938@zzz \
--to=ebiggers3@gmail.com \
--cc=linux-btrfs@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.