From: Peter Zijlstra <peterz@infradead.org>
To: tglx@linutronix.de, mingo@kernel.org, will@kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, elver@google.com,
paulmck@kernel.org, rostedt@goodmis.org, rjw@rjwysocki.net,
peterz@infradead.org
Subject: [RFC][PATCH 0/3] Tracing, Idle, RCU and such goodness
Date: Fri, 07 Aug 2020 21:23:36 +0200 [thread overview]
Message-ID: <20200807192336.405068898@infradead.org> (raw)
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.
next reply other threads:[~2020-08-07 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 19:23 Peter Zijlstra [this message]
2020-08-07 19:23 ` [RFC][PATCH 1/3] sched,idle,rcu: Push rcu_idle deeper into the idle path Peter Zijlstra
2020-08-07 19:23 ` [RFC][PATCH 2/3] locking,entry: #PF vs TRACE_IRQFLAGS Peter Zijlstra
2020-08-07 20:21 ` Steven Rostedt
2020-08-10 11:57 ` peterz
2020-08-10 12:05 ` David Laight
2020-08-10 13:49 ` peterz
2020-08-07 19:23 ` [RFC][PATCH 3/3] lockdep,trace: Expose tracepoints Peter Zijlstra
2020-08-07 20:34 ` Steven Rostedt
2020-08-10 12:26 ` [RFC][PATCH v1.1 " peterz
2020-08-10 9:55 ` [RFC][PATCH 0/3] Tracing, Idle, RCU and such goodness Marco Elver
2020-08-10 12:11 ` peterz
2020-08-11 16:08 ` Paul E. McKenney
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 \
--in-reply-to=20200807192336.405068898@infradead.org \
--to=peterz@infradead.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).