From: Tejun Heo <tj@kernel.org>
To: Nikolay Borisov <kernel@kyup.com>
Cc: 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: Wed, 13 Jul 2016 14:07:24 -0400 [thread overview]
Message-ID: <20160713180724.GI4065@mtj.duckdns.org> (raw)
In-Reply-To: <577A6177.60602@kyup.com>
Hello,
On Mon, Jul 04, 2016 at 04:15:35PM +0300, Nikolay Borisov wrote:
> So the btrfs fs was created inside a loop device and mounted with -o loop.
> Evidently from the oops it seems that this is the normal umount path, meaning
> that no device hot plugging was in action. Unfortunately I don't have a reproducer.
> However, the workload looks like the following:
>
> 1. mount -t btrfs -o compress=zlib -o subvol="${subvol}" -o loop "${storage_file}" "${mount_point}"
> 2. Do reads/writes (rsync) (dirtying some pages)
> 3. umount "${mount_point}"
I see. Yeah, normal umount path does destroy the block device and can
trigger the bug. Please ping if the issue happens again with the
patches applied.
Thanks.
--
tejun
prev parent reply other threads:[~2016-07-13 18:07 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
2016-07-04 13:15 ` Nikolay Borisov
2016-07-13 18:07 ` Tejun Heo [this message]
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=20160713180724.GI4065@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=dvyukov@google.com \
--cc=jack@suse.com \
--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).