linux-ext4 - [Bug 203317] WARNING: CPU: 2 PID: 925 at fs/ext4/inode.c:3897 ext4_set_page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-203317-13602-VsdkJSxwmO@https.bugzilla.kernel.org/>
Date:   Wed, 14 Aug 2019 16:36:28 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 203317] WARNING: CPU: 2 PID: 925 at fs/ext4/inode.c:3897
 ext4_set_page_dirty+0x39/0x50

https://bugzilla.kernel.org/show_bug.cgi?id=203317

--- Comment #5 from howaboutsynergy is abandoned account everywhere (howaboutsynergy@...me) ---
Just to be clear, this is a regression that commit
aa56a292ce623734ddd30f52d73f527d1f3529b5 introduces, which is manifested by a
deadlock-like system freeze which is different than the one that le9g.patch is
addressing. (all of this is mentioned in prev. comment)

I don't know what the fix is, but temporarily reverting that commit gets rid of
the regression.

Please let me know whether I should stick around if you want me to test any new
patch about this or not. (because otherwise I won't even check my
email/notifications for this account, anymore)

Cheers.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.