linux-kernel - Re: [PATCH 1/7 5.10.y] tracing: Define the is_signed

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: <2025092123-arming-tannery-c17e@gregkh>
Date: Sun, 21 Sep 2025 19:30:17 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: "Farber, Eliav" <farbere@...zon.com>
Cc: "luc.vanoostenryck@...il.com" <luc.vanoostenryck@...il.com>,
	"rostedt@...dmis.org" <rostedt@...dmis.org>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"sj@...nel.org" <sj@...nel.org>,
	"David.Laight@...lab.com" <David.Laight@...lab.com>,
	"Jason@...c4.com" <Jason@...c4.com>,
	"andriy.shevchenko@...ux.intel.com" <andriy.shevchenko@...ux.intel.com>,
	"bvanassche@....org" <bvanassche@....org>,
	"keescook@...omium.org" <keescook@...omium.org>,
	"linux-sparse@...r.kernel.org" <linux-sparse@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Chocron, Jonathan" <jonnyc@...zon.com>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH 1/7 5.10.y] tracing: Define the is_signed_type() macro
 once

On Wed, Sep 17, 2025 at 10:37:31AM +0000, Farber, Eliav wrote:
> > On Tue, Sep 16, 2025 at 09:22:53PM +0000, Eliav Farber wrote:
> > > From: Bart Van Assche <bvanassche@....org>
> > >
> > > commit 92d23c6e94157739b997cacce151586a0d07bb8a upstream.
> >
> > This is only in 6.1, and not other trees, why is it needed here?
> 
> It exists also in 5.15:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/include/linux/overflow.h?h=v5.15.193&id=ed6e37e30826b12572636c6bbfe6319233690c90

What?  Ugh, duplicate commit ids.  What a mess :(

Fair enough, I can take this, and I want to, but as this really causes a
problem with our scripts, perhaps use the git id that is references in
the other kernel versions as well so that things don't look totally
wrong?

thanks,

greg k-h