On Tue, 2025-07-01 at 14:03 +0200, Christian Brauner wrote: > On Tue, 27 May 2025 11:08:36 +0200, Nam Cao wrote: > > The ready event list of an epoll object is protected by read-write > > semaphore: > > > > - The consumer (waiter) acquires the write lock and takes items. > > - the producer (waker) takes the read lock and adds items. > > > > The point of this design is enabling epoll to scale well with large number > > of producers, as multiple producers can hold the read lock at the same > > time. > > > > [...] > > Applied to the vfs.fixes branch of the vfs/vfs.git tree. > Patches in the vfs.fixes branch should appear in linux-next soon. > Please report any outstanding bugs that were missed during review in a > new review to the original patch series allowing us to drop it. Hi, After upgrading my kernel to the recent mainline I've encountered some stability issue, like: - When GDM started gnome-shell, the screen often froze and the only thing I could do was to switch into a VT and reboot. - Sometimes gnome-shell started "fine" but then starting an application (like gnome-console) needed to wait for about a minute. - Sometimes the system shutdown process hangs waiting for a service to stop. - Rarely the system boot process hangs for no obvious reason. Most strangely in all the cases there are nothing alarming in dmesg or system journal. I'm unsure if this is the culprit but I'm almost sure it's the trigger. Maybe there's some race condition in my userspace that the priority inversion had happened to hide... but anyway reverting this patch seemed to "fix" the issue. Any thoughts or pointers to diagnose further? -- Xi Ruoyao <xry111@xxxxxxxxxxx>
