Re: GPF in __mark_inode_dirty due to locked_inode_to_wb_and_lock_list returning NULL

From	Tejun Heo <tj@kernel.org>
Newsgroups	linux.kernel
Subject	Re: GPF in __mark_inode_dirty due to locked_inode_to_wb_and_lock_list returning NULL
Date	2016-07-13 20:10 +0200
Message-ID	<rUwLD-6Du-1@gated-at.bofh.it> (permalink)
References	<rPIaJ-to-9@gated-at.bofh.it> <rQ3yy-5kw-17@gated-at.bofh.it> <rQaA2-13g-13@gated-at.bofh.it> <rRbX4-63R-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: GPF in __mark_inode_dirty due to  locked_inode_to_wb_and_lock_list returning NULL Tejun Heo <tj@kernel.org> - 2016-07-13 20:10 +0200

csiph-web