linux-kernel - Re: limits.h in tools/

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]

Date: Wed, 24 Apr 2024 10:46:10 -0400
From: "Liam R. Howlett" <Liam.Howlett@...cle.com>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>, linux-kernel@...r.kernel.org,
        Willy Tarreau <w@....eu>,
        Thomas Weißschuh <linux@...ssschuh.net>,
        Andrew Morton <akpm@...ux-foundation.org>, willy@...radead.org,
        Namhyung Kim <namhyung@...nel.org>
Subject: Re: limits.h in tools/

* Liam R. Howlett <Liam.Howlett@...cle.com> [240424 10:40]:
> * Andy Shevchenko <andriy.shevchenko@...el.com> [240424 10:19]:
> ...
> 
> > > > On Tue, Apr 23, 2024 at 10:29:31PM +0300, Andy Shevchenko wrote:
> > > > > On Tue, Apr 23, 2024 at 04:22:01PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > > > On Tue, Apr 23, 2024 at 09:58:07PM +0300, Andy Shevchenko wrote:
> > > > > > > It seems tons of the code in tools include linux/limits.h. But I haven't found
> > > > > > > where do we copy it. Any pointers?
> > > > > > > 
> > > > > > > Based on the discussion 20220603183231.15159C385A9@...p.kernel.org.
> > > 
> > > I was unable to locate this discussion.
> > 
> >   `b4 mbox 20220603183231.15159C385A9@...p.kernel.org`
> > 
> > works for me
> > 
> > $ b4 mbox 20220603183231.15159C385A9@...p.kernel.org
> > Grabbing thread from lore.kernel.org/all/20220603183231.15159C385A9@...p.kernel.org/t.mbox.gz
> > 8 messages in the thread
> > Saved ./20220603183231.15159C385A9@...p.kernel.org.mbx
> 
> Interesting, I usually use the web search for the id and that failed me
> in this case.  I use b4 for patch fetching and reviewing.

Okay, I see what this is about.  Thanks.

We should probably switch to using the right header in all locations in
our testing directory.

Thanks,
Liam