linux-ext4 - [Bug 209275] Graphics freeze after WARNING: CPU: 2 PID: 156207 at fs/ext4/inode.c:3599 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] [day] [month] [year] [list]

Date:   Thu, 24 Sep 2020 00:22:54 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 209275] Graphics freeze after WARNING: CPU: 2 PID: 156207 at
 fs/ext4/inode.c:3599 ext4_set_page_dirty+0x3e/0x50

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

--- Comment #6 from Monthero Ronald (rhmcruiser@...il.com) ---
(In reply to Dennis Wagelaar from comment #4)
> This bug no longer occurs under kernel 5.8.9-101.fc31.x86_64 - closing.
Ah good to know issue is resolved with upgrade to newer kernel. (Probbaly the
issue was within the gnome-shell where the above stack was indicating a use
after free sort of condition in the gnome userspace code causing core dumps.  


ep 15 08:23:46 styx gnome-shell[67420]: #9   55a8b19fc420 i  
resource:///org/gnome/gjs/modules/overrides/Gio.js:169 (7fba6c0d3e50 @ 39)
Sep 15 08:23:46 styx gnome-shell[67420]: == Stack trace for context
0x55a8ac63e3a0 ==
Sep 15 08:23:46 styx gnome-shell[67420]: #0   55a8b19fc6d8 i  
/usr/share/gnome-shell/extensions/gamemode@...istian.kellner.me/extension.js:231
(7fba10824820 @ 287)
Sep 15 08:23:46 styx gnome-shell[67420]: #1   7ffe62146c90 b   self-hosted:977
(7fba45130a60 @ 413)
Sep 15 08:23:46 styx gnome-shell[67420]: #2   7ffe62146d70 b  
resource:///org/gnome/gjs/modules/signals.js:135 (7fba6c0c6040 @ 376)
Sep 15 08:23:46 styx journal[67420]: Object St.Icon (0x55a8ad298110), has been
already deallocated — impossible to access it. This might be caused by the
object having been destroyed from C code using something such as destroy(),
dispose(), or remove() vfuncs.

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