[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 8 Aug 2016 17:02:13 -0400
From: Chris Mason <clm@...com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
kernel test robot <xiaolong.ye@...el.com>,
Josef Bacik <jbacik@...com>, David Sterba <dsterba@...e.com>
CC: Mike Snitzer <snitzer@...hat.com>,
Akira Hayakawa <ruby.wktk@...il.com>,
LKML <linux-kernel@...r.kernel.org>, LKP <lkp@...org>,
linux-btrfs <linux-btrfs@...r.kernel.org>
Subject: Re: [lkp] [dm flakey] 99f3c90d0d: WARNING: CPU: 20 PID: 1027 at
fs/btrfs/extent-tree.c:2973 btrfs_run_delayed_refs+0x2c5/0x2f0 [btrfs]
On 08/08/2016 02:27 PM, Linus Torvalds wrote:
> This report should probably have gone to the btrfs people, although it
> doesn't really look like a bug.
>
> It looks like it's just dm-flakey now returning more errors, and
> causing btrfs to complain more.
>
> Which seems entirely expected.
>
> Maybe the robot just was testing a error case that didn't actually
> happen before.
Yeah, this warning in btrfs is much too verbose. I've been meaning to
toss it under a debugging conditional because it makes common hardware
problems look like software problems. It also spams dmesg during xfstests.
Thanks, I've been meaning to fix it up.
-chris
Powered by blists - more mailing lists