[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230425181827.219128101@linutronix.de>
Date: Tue, 25 Apr 2023 20:48:55 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: LKML <linux-kernel@...r.kernel.org>
Cc: Frederic Weisbecker <frederic@...nel.org>,
Anna-Maria Behnsen <anna-maria@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Sebastian Siewior <bigeasy@...utronix.de>,
syzbot+5c54bd3eb218bb595aa9@...kaller.appspotmail.com,
Dmitry Vyukov <dvyukov@...gle.com>,
Michael Kerrisk <mtk.manpages@...il.com>
Subject: [patch 00/20] posix-timers: Fixes and cleanups
Hi!
A recent syzcaller/KCSAN report about a data race and an actually broken
loop termination due to that race made me look deeper into the posix timer
code.
Aside of the loop termination issue this unearthed another issue in the
exit() path where timer deletion might livelock on RT enabled kernels.
While going through the code with a fine comb, I stumbled over another
place which needs READ/WRITE_ONCE() annotations, tons of outdated and/or
uncomprehensible comments and a bunch of silly code.
The series has therefore a larger set of cleanups on top of the two fixes.
It is based on
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
and also availble from git:
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git timers/posix
Thanks,
tglx
---
include/linux/sched/signal.h | 2
kernel/time/posix-timers.c | 523 ++++++++++++++++++++++++++-----------------
2 files changed, 321 insertions(+), 204 deletions(-)
Powered by blists - more mailing lists