mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	kernel test robot <xiaolong.ye@intel.com>,
	Josef Bacik <jbacik@fb.com>, David Sterba <dsterba@suse.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
	Akira Hayakawa <ruby.wktk@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
	linux-btrfs <linux-btrfs@vger.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]
Date: Mon, 8 Aug 2016 17:02:13 -0400	[thread overview]
Message-ID: <652374b9-1457-0409-b5eb-b253efb7d5fd@fb.com> (raw)
In-Reply-To: <CA+55aFzFFKaTMfDUmrV5QvLq0PsmmNrRYqVOLLujyQq7oa4Nkg@mail.gmail.com>



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

      reply	other threads:[~2016-08-08 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08  8:00 kernel test robot
2016-08-08 18:27 ` Linus Torvalds
2016-08-08 21:02   ` Chris Mason [this message]

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=652374b9-1457-0409-b5eb-b253efb7d5fd@fb.com \
    --to=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ruby.wktk@gmail.com \
    --cc=snitzer@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xiaolong.ye@intel.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
all inboxes | Powered by JetHome®