linux-kernel - Re: [GIT PULL] probes updates for v6.10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20240519084624.dce1a405a42684189fb356fe@kernel.org>
Date: Sun, 19 May 2024 08:46:24 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrii Nakryiko <andrii@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
 Jonathan Haslam <jonathan.haslam@...il.com>, Kui-Feng Lee
 <thinker.li@...il.com>, Stephen Brennan <stephen.s.brennan@...cle.com>, Ye
 Bin <yebin10@...wei.com>, Steven Rostedt <rostedt@...dmis.org>,
 linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] probes updates for v6.10

On Sat, 18 May 2024 08:55:55 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Sat, 18 May 2024 at 07:38, Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> > Ah, and I missed to build it with W=1.
> 
> Note that I do *not* at all expect people to build with W=1. It gets
> very noisy depending on your compiler version etc, and a lot of the
> W=1 errors are not at all worth worrying about.
> 
> But what I do expect is for merge window pull  requests to have been
> in linux-next, which will give it at least reasonable build coverage
> from the bots,

This is completely my fault that I forgot to push my probes/for-next
and made a pull request to you. I will push the for-next before -rc6 and
if I forgot it I will defer it to next for-next.

> 
> I'm not sure whether it was because I built witch clang (which gives
> some warnings that gcc does not, and vice versa) or whether it was
> just that my clang build has a different Kconfig. Regardless, if this
> had been in linux-next, I'm pretty sure that it would have been found
> before I hit it.

Yes, I missed to build check with clang. I'll make sure to check with
both clang and gcc for release.

I'm sorry for causing you trouble and thanks for fixing the it.

Thank you,

-- 
Masami Hiramatsu (Google) <mhiramat@...nel.org>