From: Tejun Heo <tj@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Nikolay Borisov <kernel@kyup.com>, Jan Kara <jack@suse.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
dvyukov@google.com, linux-btrfs@vger.kernel.org,
SiteGround Operations <operations@siteground.com>
Subject: Re: GPF in __mark_inode_dirty due to locked_inode_to_wb_and_lock_list returning NULL
Date: Fri, 1 Jul 2016 12:38:27 -0500 [thread overview]
Message-ID: <20160701173827.GE28719@htj.duckdns.org> (raw)
In-Reply-To: <20160701100050.GC22922@quack2.suse.cz>
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
next prev parent reply other threads:[~2016-07-01 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 11:18 GPF in __mark_inode_dirty due to locked_inode_to_wb_and_lock_list returning NULL Nikolay Borisov
2016-07-01 10:00 ` Jan Kara
2016-07-01 17:38 ` Tejun Heo [this message]
2016-07-04 13:15 ` Nikolay Borisov
2016-07-13 18:07 ` Tejun Heo
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=20160701173827.GE28719@htj.duckdns.org \
--to=tj@kernel.org \
--cc=dvyukov@google.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=kernel@kyup.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=operations@siteground.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;
as well as URLs for NNTP newsgroup(s).