From: Tomasz Chmielewski <tch@virtall.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/inode.c:1593! with 3.13.0-rc7
Date: Mon, 13 Jan 2014 11:35:08 +0100 [thread overview]
Message-ID: <20140113113508.004513cb@virtall.com> (raw)
In-Reply-To: <52D3905E.9090606@cn.fujitsu.com>
I've applied it to 3.13-rc8, let's see if it helps.
--
Tomasz Chmielewski
On Mon, 13 Jan 2014 15:06:06 +0800
Wang Shilong <wangsl.fnst@cn.fujitsu.com> wrote:
> On 01/13/2014 06:47 AM, Tomasz Chmielewski wrote:
>
> Hello Tomasz,
>
> Chris recently sent a patch that addressed a race condition with
> loading inode, i think it might be related to your first dmesg
> warning.
>
> Chris' patch url can be seen:
> https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg30332.html
>
> Thanks,
> Wang
> > Just had this on a btrfs filesystem running 3.13-rc7.
> >
> > The filesystem was working fine till now and was passing balance and
> > scrub properly without any issues a couple of days ago:
> >
> > [273059.042280] ------------[ cut here ]------------
> > [273059.042369] WARNING: CPU: 6 PID: 20754 at fs/btrfs/inode.c:4721
> > inode_tree_add+0xc2/0x13f [btrfs]() [273059.042484] Modules linked
> > in: ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4
> > nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables cpufreq_ondemand
> > cpufreq_conservative cpufreq_powersave cpufreq_stats bridge stp llc
> > ipv6 btrfs xor raid6_pq zlib_deflate loop lpc_ich mfd_core i2c_i801
> > i2c_core pcspkr button video ehci_pci ehci_hcd acpi_cpufreq ext4
> > crc16 jbd2 mbcache raid1 sg sd_mod ahci libahci libata scsi_mod
> > r8169 mii [273059.042901] CPU: 6 PID: 20754 Comm: btrfs-endio-wri
> > Tainted: G W 3.13.0-rc7 #1 [273059.043014] Hardware name:
> > System manufacturer System Product Name/P8H77-M PRO, BIOS 1101
> > 02/04/2013 [273059.043129] 0000000000000009 ffff8807a7959b18
> > ffffffff81389887 0000000000000006 [273059.043245] 0000000000000000
> > ffff8807a7959b58 ffffffff810370a9 ffff8801b0d21040 [273059.043360]
> > ffffffffa027d623 ffff880637209968 ffff88020a8bde88 ffff880667c1b800
> > [273059.043476] Call Trace: [273059.043536] [<ffffffff81389887>]
> > dump_stack+0x46/0x58 [273059.043599] [<ffffffff810370a9>]
> > warn_slowpath_common+0x77/0x91 [273059.043674]
> > [<ffffffffa027d623>] ? inode_tree_add+0xc2/0x13f [btrfs]
> > [273059.043738] [<ffffffff810370d8>] warn_slowpath_null+0x15/0x17
> > [273059.043810] [<ffffffffa027d623>] inode_tree_add+0xc2/0x13f
> > [btrfs] [273059.043885] [<ffffffffa02840cb>]
> > btrfs_iget+0x46c/0x4b6 [btrfs] [273059.043958]
> > [<ffffffffa028421a>] relink_extent_backref+0x105/0x6cf [btrfs]
> > [273059.044032] [<ffffffffa0284fa1>]
> > btrfs_finish_ordered_io+0x7bd/0x877 [btrfs] [273059.044155]
> > [<ffffffffa028506b>] finish_ordered_fn+0x10/0x12 [btrfs]
> > [273059.044232] [<ffffffffa02a00d1>] worker_loop+0x15e/0x495
> > [btrfs] [273059.044307] [<ffffffffa029ff73>] ?
> > btrfs_queue_worker+0x269/0x269 [btrfs] [273059.044372]
> > [<ffffffff8104ee9a>] kthread+0xcd/0xd5 [273059.044434]
> > [<ffffffff8104edcd>] ? kthread_freezable_should_stop+0x43/0x43
> > [273059.044498] [<ffffffff8138e6bc>] ret_from_fork+0x7c/0xb0
> > [273059.044560] [<ffffffff8104edcd>] ?
> > kthread_freezable_should_stop+0x43/0x43 [273059.044624] ---[ end
> > trace 714ee71af93c5bba ]--- [366782.707007] ------------[ cut here
> > ]------------
> >
next prev parent reply other threads:[~2014-01-13 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 22:47 kernel BUG at fs/btrfs/inode.c:1593! with 3.13.0-rc7 Tomasz Chmielewski
2014-01-13 1:24 ` Gui Hecheng
2014-01-13 10:13 ` Tomasz Chmielewski
2014-01-13 7:06 ` Wang Shilong
2014-01-13 10:35 ` Tomasz Chmielewski [this message]
2014-01-22 12:07 ` Tomasz Chmielewski
2014-01-22 12:19 ` Filipe David Manana
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=20140113113508.004513cb@virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.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