linux-kernel - Re: Kernel warning at fs/btrfs/inode.c:8693 btrfs_destroy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJCQCtRZxrR8yLM04oDKNhMbPUw4rN5dtMM2y245p6hM46mhUA@mail.gmail.com>
Date:	Thu, 26 Mar 2015 21:49:20 -0600
From:	Chris Murphy <lists@...orremedies.com>
To:	Nikolaus Rath <Nikolaus@...h.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Btrfs BTRFS <linux-btrfs@...r.kernel.org>
Subject: Re: Kernel warning at fs/btrfs/inode.c:8693 btrfs_destroy_inode+0x1fa/0x2a0
 [btrfs]()

On Thu, Mar 26, 2015 at 9:39 PM, Nikolaus Rath <Nikolaus@...h.org> wrote:

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

I can't answer that. I'd say use 3.18.9 or 3.19.2 if you want reduced
risk of corruption, or use the current week's rc (which is rc5) if you
can accept a bit more risk for testing purposes.

-- 
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/