[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-201631-13602-UQ4TvPeg1m@https.bugzilla.kernel.org/>
Date: Thu, 20 Dec 2018 07:41:28 +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
Jan Kara (jack@...e.cz) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #280097|0 |1
is obsolete| |
--- Comment #27 from Jan Kara (jack@...e.cz) ---
Created attachment 280103
--> https://bugzilla.kernel.org/attachment.cgi?id=280103&action=edit
mm: Dump page and PTE state and some history (v2)
I'm sorry but the patch had a bug and didn't set time when page_mkwrite() has
been called for the most common ext4 path which is taken on your machine. Here
is a fixed up patch. Can you please test again!
Also it seems you are now able to trigger the warning in under an hour? In that
case it would be plausible to bisect the kernel if the directed debugging
fails. We'll see...
--
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists