linux-kernel - Re: [GIT PULL] nolibc changes for v5.19

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: <CAHk-=wgpAHhPVSqBWb4gYT=CRJzKAZ4inmrL_kcpeNWGkcg3pg@mail.gmail.com>
Date:   Mon, 23 May 2022 11:42:48 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Kernel Team <kernel-team@...com>, Willy Tarreau <w@....eu>
Subject: Re: [GIT PULL] nolibc changes for v5.19

On Fri, May 20, 2022 at 11:24 AM Paul E. McKenney <paulmck@...nel.org> wrote:
>
> This pull request adds a number of library functions and splits this
> library into multiple files.

Well, this is annoying.

You add the rule to test and install this, and "make help" will list
"nolibc" as a target, but that is not actually true at all.

So what's the appropriate way to actually test this pull somehow?

I'm guessing it's along the lines of

    make ARCH=x86 nolibc_headers

in the tools directory, but then I got bored and decided I need to
just continue the merge window.

I've pulled this, but it all makes me go "Hmm, I'd have liked to maybe
even build test it".

                Linus