From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>,
Sumanth Gavini <sumanth.gavini@yahoo.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org, jstultz@google.com,
clingutla@codeaurora.org, mingo@kernel.org, sashal@kernel.org,
boqun.feng@gmail.com, ryotkkr98@gmail.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, "J . Avila" <elavila@google.com>
Subject: Re: [PATCH 6.1] softirq: Add trace points for tasklet entry/exit
Date: Sat, 23 Aug 2025 19:42:25 +0200 [thread overview]
Message-ID: <87ldnavsse.ffs@tglx> (raw)
In-Reply-To: <2025082257-smirk-backside-6d93@gregkh>
On Fri, Aug 22 2025 at 15:07, Greg KH wrote:
> On Tue, Aug 12, 2025 at 11:17:54AM -0500, Sumanth Gavini wrote:
>
> And I'm with John, this makes no sense as to why you need/want these. I
> think that the syzbot report is bogus, sorry. Please prove me wrong :)
It was validated by AI (Absense of Intelligence) that adding tracepoints
makes the problem go away! So why do you want extra proof?
Thanks,
tglx
next prev parent reply other threads:[~2025-08-23 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250812161755.609600-1-sumanth.gavini.ref@yahoo.com>
2025-08-12 16:17 ` [PATCH 6.1] softirq: Add trace points for tasklet entry/exit Sumanth Gavini
2025-08-21 18:40 ` Sumanth Gavini
2025-08-21 18:54 ` John Stultz
2025-08-21 21:02 ` Sumanth Gavini
2025-08-21 22:05 ` John Stultz
2025-08-22 13:07 ` Greg KH
2025-08-23 17:42 ` Thomas Gleixner [this message]
2025-09-23 13:13 ` Sumanth Gavini
2025-09-23 21:01 ` John Stultz
2025-11-12 3:16 ` [PATCH V2 " Sumanth Gavini
2025-11-17 1:06 ` Sasha Levin
2025-12-03 17:17 ` Steven Rostedt
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=87ldnavsse.ffs@tglx \
--to=tglx@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=clingutla@codeaurora.org \
--cc=elavila@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jstultz@google.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=ryotkkr98@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumanth.gavini@yahoo.com \
/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