[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-201631-13602-vLhTCyuRHs@https.bugzilla.kernel.org/>
Date: Thu, 20 Dec 2018 04:15:15 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 201631] WARNING: CPU: 11 PID: 29593 at fs/ext4/inode.c:3927
.ext4_set_page_dirty+0x70/0xb0
https://bugzilla.kernel.org/show_bug.cgi?id=201631
aneesh.kumar@...ux.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aneesh.kumar@...ux.ibm.com
--- Comment #25 from aneesh.kumar@...ux.ibm.com ---
(In reply to Benjamin Herrenschmidt from comment #24)
> Out of curiosity, how does this work in the context of pages that are GUPed
> either by a driver or by KVM when using file backed guest memory ?
>
> GUP will not "see" the mkclean or attempt at making read only...
page_mkclean_one do call
mmu_notifier_invalidate_range_start(vma->vm_mm, start, end);
--
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists