linux-kernel - Re: [PATCH] tools headers: move the nolibc header from rcutorture to tools/include/nolibc/

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181229200004.GA16717@1wt.eu>
Date:   Sat, 29 Dec 2018 21:00:04 +0100
From:   Willy Tarreau <w@....eu>
To:     "Paul E. McKenney" <paulmck@...ux.ibm.com>
Cc:     mingo@...nel.org, acme@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools headers: move the nolibc header from rcutorture to
 tools/include/nolibc/

On Sat, Dec 29, 2018 at 11:55:18AM -0800, Paul E. McKenney wrote:
> On Sat, Dec 29, 2018 at 07:30:47PM +0100, Willy Tarreau wrote:
> > On Sat, Dec 29, 2018 at 10:25:08AM -0800, Paul E. McKenney wrote:
> > > On Sat, Dec 29, 2018 at 07:04:53PM +0100, Willy Tarreau wrote:
> > > > As suggested by Ingo, this header file might benefit other tools than
> > > > just rcutorture. For now it's quite limited, but is easy to extend, so
> > > > exposing it into tools/include/nolibc/ will make it much easier to
> > > > adopt by other tools.
> > > > 
> > > > The mkinitrd.sh script in rcutorture was updated to use this new location.
> > > > 
> > > > Cc: Ingo Molnar <mingo@...nel.org>
> > > > Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
> > > > Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> > > > Signed-off-by: Willy Tarreau <w@....eu>
> > > 
> > > Thank you, Willy!
> > 
> > You're welcome!
> > 
> > > I have queued all four of these.
> > 
> > Thanks!
> > 
> > > Should there
> > > be a MAINTAINERS file entry for the new include/nolibc home for this
> > > library code?
> > 
> > Good idea, I didn't think about it. Yes, I can add one and will
> > send another patch. In case that helps I've created a repo at
> > /pub/scm/linux/kernel/git/wtarreau/nolibc.git
> 
> And I have queued that one as well, thank you!
> 
> I am happy to curate nolibc patches indefinitely, but should some other
> pathway to mainline become better for you, just let me know.

Oh perfect, thank you. I'm always having difficulties with processes,
so having a known working path to mainline is indeed a much appreciated
help!

Thanks,
Willy