linux-kernel - Re: GPF in __mark_inode_dirty due to locked_inode_to_wb_and_lock

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]

Message-ID: <20160701173827.GE28719@htj.duckdns.org>
Date:	Fri, 1 Jul 2016 12:38:27 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Jan Kara <jack@...e.cz>
Cc:	Nikolay Borisov <kernel@...p.com>, Jan Kara <jack@...e.com>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	dvyukov@...gle.com, linux-btrfs@...r.kernel.org,
	SiteGround Operations <operations@...eground.com>
Subject: Re: GPF in __mark_inode_dirty due to
 locked_inode_to_wb_and_lock_list returning NULL

On Fri, Jul 01, 2016 at 12:00:50PM +0200, Jan Kara wrote:
> Hello,
> 
> On Thu 30-06-16 14:18:14, Nikolay Borisov wrote:
> > In light of the discussion in https://patchwork.kernel.org/patch/9187411/ and 
> > the discussion at https://groups.google.com/forum/#!topic/syzkaller/XvxH3cBQ134
> 
> Well, it looks it is also some bdi_writeback lifetime issue but I don't see
> how it would be related to I_DIRTY_TIME issues. There were couple of fixes
> related to bdi_writeback issues from Tejun since 4.4. Maybe Tejun can tell
> you whether he's seen this or not...

Yeah, this could be the same problem from the blkdev detach path.
Nikolay, was there any block device hot unplugging going on?  If not,
do you have a reproducer?

Thanks.

-- 
tejun