linux-kernel - [RFC][PATCH 0/3] Tracing, Idle, RCU and such goodness

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 07 Aug 2020 21:23:36 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     tglx@...utronix.de, mingo@...nel.org, will@...nel.org
Cc:     x86@...nel.org, linux-kernel@...r.kernel.org, elver@...gle.com,
        paulmck@...nel.org, rostedt@...dmis.org, rjw@...ysocki.net,
        peterz@...radead.org
Subject: [RFC][PATCH 0/3] Tracing, Idle, RCU and such goodness

Hi,

Syzbot report:

  https://lkml.kernel.org/r/000000000000e3068105ac405407@google.com

triggered a whole bunch of fallout.

These 3 patches are in reverse order of discovery. With them applied the
reproducer no longer triggers and the machine boots without errors.

I also spend half the day trying to rewrite TRACE_IRQFLAGS, but so far haven't
had success. I have the feeling that there's something slightly simpler hiding
in there, but so far it doesn't want to come out.

Please, look carefully, this is all tricky code, and it's been a long and hot
day here, mistakes are almost guaranteed :/

I also want to remove the _rcuidle() from trace_preemptirq.c, but given
this was quite enough, I didn't touch those.