linux-kernel - Re: btrfs: kernel BUG at mm/page-writeback.c:2286!

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 May 2015 09:43:10 -0400
From:	Chris Mason <clm@...com>
To:	Govindarajulu Varadarajan <_govind@....com>,
	<linux-btrfs@...r.kernel.org>, <linux-nfs@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
CC:	<jbacik@...com>, <dsterba@...e.cz>
Subject: Re: btrfs: kernel BUG at mm/page-writeback.c:2286!

On 05/19/2015 03:55 AM, Govindarajulu Varadarajan wrote:
> Hi all
> 
> I am seeing the following crash on my btrfs filesystem with nfs export.
> If I disable the nfs share and reboot, I do not hit the crash. Look like
> the crash happens on btrfs with nfs export.
> 
> Is this a known issue? Has anyone else faced this? Let me know if you
> need more
> information.
> 
> Thanks
> 
> mm/page-writeback.c:2286:
> int clear_page_dirty_for_io(struct page *page) {
>         struct address_space *mapping = page_mapping(page);
> 
> 2286--->BUG_ON(!PageLocked(page));
> 
> [  166.769868] BTRFS info (device sdf): no csum found for inode 1154
> start 43192320
> [  166.774334] BTRFS info (device sdf): csum failed ino 1154 extent
> 4434247680 csum 1388825687 wanted 0 mirror 0


Josef and I both missed this the first time you pasted it, but the
unlocked page is almost certainly related to this csum error.  While
we're looking at things can you please scrub?


-chris

--
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/