From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Menglong Dong <menglong8.dong@gmail.com>,
Thorsten Blum <thorsten.blum@linux.dev>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] probes: Update for v6.18
Date: Mon, 6 Oct 2025 09:27:43 +0900 [thread overview]
Message-ID: <20251006092743.295205e486acf1b69ca61b89@kernel.org> (raw)
In-Reply-To: <CAHk-=wg6=DwTD7xT3=Zya-ytYrtS2969KtnTWRPskq5fx2Ev+g@mail.gmail.com>
On Sun, 5 Oct 2025 09:20:29 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, 2 Oct 2025 at 16:44, Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > - wprobe: Introduce a watchpoint probe event based on hw_breakpoint.
>
> This doesn't even build.
>
> kernel/trace/trace_wprobe.c: In function ‘__register_trace_wprobe’:
> kernel/trace/trace_wprobe.c:176:20: error: cast to generic address
> space pointer from disjoint ‘__seg_gs’ address space pointer [-Werror]
>
> and I see from the code that it has tried to brute-force it with an
> ugly cast, and it still is horribly horribly wrong.
Hmm, I applogise this error. I locally ran build tests and it passed.
But I might missed something.
>
> The fix for compiler errors is basically never to just add a random
> cast. That will just make things worse, and in this case that
> 'IS_ERR()' function literally exists to find bad users like this.
OK.
>
> I wondered why this hadn't been reported in linux-next, and the reason
> appears simple: none of this has BEEN in linux-next.
>
> So no. I'm not pulling this. This violates all the regular rules for
> sending me new development, and then it doesn't even compile.
>
> Since the pointer is a percpu pointer, the trivial fix is ato use the
> per-cpu specific functions (IS_ERR_PCPU(), PTR_ERR_PCPU(), etc).
OK.
>
> However, since this wasn't in linux-next, that's not what I'm doing.
>
> This is not getting pulled for 6.18 AT ALL, and for 6.19 it had better
> be in linux-next for a LOONG time.
Got it. Sorry about my mistake. Let me fix it on for-next, and
keep checking it is in linux-next and tested well.
Thank you,
>
> Linus
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-10-06 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 23:44 [GIT PULL] probes: Update for v6.18 Masami Hiramatsu
2025-10-05 16:20 ` Linus Torvalds
2025-10-06 0:27 ` Masami Hiramatsu [this message]
2025-10-06 0:50 ` Masami Hiramatsu
2025-10-06 3:09 ` Linus Torvalds
2025-10-06 12:01 ` Masami Hiramatsu
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=20251006092743.295205e486acf1b69ca61b89@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=rostedt@goodmis.org \
--cc=thorsten.blum@linux.dev \
--cc=torvalds@linux-foundation.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