Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1442735 > unrolled thread
| Started by | Tejun Heo <tj@kernel.org> |
|---|---|
| First post | 2016-07-13 20:10 +0200 |
| Last post | 2016-07-13 20:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Tejun Heo <tj@kernel.org> |
|---|---|
| Date | 2016-07-13 20:10 +0200 |
| Subject | Re: GPF in __mark_inode_dirty due to locked_inode_to_wb_and_lock_list returning NULL |
| Message-ID | <rUwLD-6Du-1@gated-at.bofh.it> |
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 top | Article view | linux.kernel
csiph-web