linux-kernel - Re: v5.14-rc3-rt1 losing wakeups?

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: <20210802082545.bykz23s3ouwa4drn@linutronix.de>
Date:   Mon, 2 Aug 2021 10:25:45 +0200
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     Mike Galbraith <efault@....de>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-rt-users@...r.kernel.org,
        Steven Rostedt <rostedt@...dmis.org>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: v5.14-rc3-rt1 losing wakeups?

On 2021-08-02 09:18:34 [+0200], Mike Galbraith wrote:
> Nope.  Before I even reverted the wake_q bits, I assembled a tree with
> the ww_mutex changes completely removed to be absolutely certain that
> they were innocent, and it indeed did retain its lost wakeup woes
> despite complete loss of newfangled ww_mutex.  5.13-rt acquired those
> same wakeup woes by receiving ONLY the wake_q bits, and 5.14-rt was
> cured of those woes by ONLY them being reverted. I'm not seeing the
> why, but those bits are either the source or the trigger of 5.14-rt
> lost wakeup woes... they're toxic in some way shape fashion or form.

Okay. So the ww-mutex bits are not the cure then. All you do is booting
KDE/Plasma in kvm with virtio as GPU or did I mix up things?

> 	-Mike

Sebastian