public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel warning at fs/btrfs/inode.c:8693 btrfs_destroy_inode+0x1fa/0x2a0 [btrfs]()
Date: Thu, 26 Mar 2015 20:39:14 -0700	[thread overview]
Message-ID: <87sicrf6sd.fsf@vostro.rath.org> (raw)
In-Reply-To: <CAJCQCtTJ9wPfpLXtC+SQdpfcDww+H1_u=kjcmGe=CZtJSAkEmA@mail.gmail.com> (Chris Murphy's message of "Thu, 26 Mar 2015 21:21:36 -0600")

On Mar 26 2015, Chris Murphy <lists@colorremedies.com> wrote:
> On Thu, Mar 26, 2015 at 6:38 PM, Nikolaus Rath <Nikolaus@rath.org> wrote:
>
>> I'm running 4.0-rc3, and I'm regularly getting these warnings in my
>> kernel log:
>
>> Mar 26 17:31:13 vostro kernel: [21480.088682] WARNING: CPU: 0 PID:
>> 28958 at fs/btrfs/inode.c:8693 btrfs_destroy_inode+0x1fa/0x2a0
>> [btrfs]()
>
> It's known.
> https://lkml.org/lkml/2015/3/7/41

Thanks. Does this mean that I risk data corruption when using btrfs with
4.0-rc3, or is this relatively harmless?

Best,
-Nikolaus
-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

  reply	other threads:[~2015-03-27  3:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  0:38 Kernel warning at fs/btrfs/inode.c:8693 btrfs_destroy_inode+0x1fa/0x2a0 [btrfs]() Nikolaus Rath
2015-03-27  3:21 ` Chris Murphy
2015-03-27  3:39   ` Nikolaus Rath [this message]
2015-03-27  3:49     ` Chris Murphy

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=87sicrf6sd.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@colorremedies.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