From: Thomas Gleixner <firstname.lastname@example.org> To: LKML <email@example.com> Cc: Marco Elver <firstname.lastname@example.org>, kasan-dev <email@example.com>, Peter Zijlstra <firstname.lastname@example.org>, "Paul E. McKenney" <email@example.com>, Ingo Molnar <firstname.lastname@example.org>, Frederic Weisbecker <email@example.com>, Will Deacon <firstname.lastname@example.org>, Naresh Kamboju <email@example.com> Subject: [patch 0/3] tick: Annotate and document the intentionaly racy tick_do_timer_cpu Date: Sun, 06 Dec 2020 22:12:53 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) There have been several reports about KCSAN complaints vs. the racy access to tick_do_timer_cpu. The syzbot moderation queue has three different patterns all related to this. There are a few more... As I know that this is intentional and safe, I did not pay much attention to it, but Marco actually made me feel bad a few days ago as he explained that these intentional races generate too much noise to get to the dangerous ones. There was an earlier attempt to just silence KCSAN by slapping READ/WRITE once all over the place without even the faintiest attempt of reasoning, which is definitely the wrong thing to do. The bad thing about tick_do_timer_cpu is that its only barely documented why it is safe and works at all, which makes it extremly hard for someone not really familiar with the code to come up with reasoning. So Marco made me fast forward that item in my todo list and I have to admit that it would have been damned helpful if that Gleixner dude would have added proper comments in the first place. Would have spared a lot of brain twisting. :) Staring at all usage sites unearthed a few silly things which are cleaned up upfront. The actual annotation uses data_race() with proper comments as READ/WRITE_ONCE() does not really buy anything under the assumption that the compiler does not play silly buggers and tears the 32bit stores/loads into byte wise ones. But even that would cause just potentially shorter idle sleeps in the worst case and not a complete malfunction. Thanks, tglx ---- tick-common.c | 55 +++++++++++++++++++++++++++------ tick-sched.c | 96 ++++++++++++++++++++++++++++++++++++++++++---------------- 2 files changed, 117 insertions(+), 34 deletions(-)
next reply other threads:[~2020-12-06 21:21 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-06 21:12 Thomas Gleixner [this message] 2020-12-06 21:12 ` [patch 1/3] tick: Remove pointless cpu valid check in hotplug code Thomas Gleixner 2020-12-07 11:59 ` Peter Zijlstra 2020-12-07 17:44 ` Thomas Gleixner 2020-12-11 22:21 ` Frederic Weisbecker 2020-12-12 0:16 ` Thomas Gleixner 2020-12-12 1:20 ` Frederic Weisbecker 2020-12-11 22:31 ` Frederic Weisbecker 2020-12-16 10:50 ` [tip: timers/urgent] " tip-bot2 for Thomas Gleixner 2020-12-06 21:12 ` [patch 2/3] tick/sched: Remove bogus boot "safety" check Thomas Gleixner 2020-12-11 22:41 ` Frederic Weisbecker 2020-12-16 10:50 ` [tip: timers/urgent] " tip-bot2 for Thomas Gleixner 2020-12-06 21:12 ` [patch 3/3] tick: Annotate tick_do_timer_cpu data races Thomas Gleixner 2020-12-07 12:09 ` Peter Zijlstra 2020-12-07 17:46 ` Thomas Gleixner 2020-12-07 18:19 ` Marco Elver 2020-12-07 19:43 ` Thomas Gleixner 2020-12-07 19:44 ` Paul E. McKenney 2020-12-07 21:46 ` Thomas Gleixner 2020-12-07 22:38 ` Paul E. McKenney 2020-12-07 22:46 ` Thomas Gleixner 2020-12-07 22:55 ` Paul E. McKenney 2020-12-08 8:11 ` Peter Zijlstra 2020-12-08 15:03 ` Paul E. McKenney 2020-12-16 0:27 ` Thomas Gleixner 2020-12-16 21:19 ` Paul E. McKenney 2020-12-16 21:23 ` Thomas Gleixner 2020-12-16 21:32 ` Paul E. McKenney 2020-12-17 10:48 ` Peter Zijlstra 2020-12-17 14:59 ` Paul E. McKenney 2020-12-08 8:01 ` Peter Zijlstra 2020-12-07 11:05 ` [patch 0/3] tick: Annotate and document the intentionaly racy tick_do_timer_cpu Marco Elver
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [patch 0/3] tick: Annotate and document the intentionaly racy tick_do_timer_cpu' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.