linux-kernel - Re: nolibc changes since 6.6-rc1 for linux-next

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]

Date:   Thu, 5 Oct 2023 17:01:22 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Shuah Khan <skhan@...uxfoundation.org>
Cc:     Thomas Weißschuh <linux@...ssschuh.net>,
        Shuah Khan <shuah@...nel.org>, Willy Tarreau <w@....eu>,
        linux-kernel@...r.kernel.org
Subject: Re: nolibc changes since 6.6-rc1 for linux-next

On Thu, Oct 05, 2023 at 03:30:52PM -0600, Shuah Khan wrote:
> On 10/5/23 14:58, Paul E. McKenney wrote:
> > On Thu, Oct 05, 2023 at 10:28:05PM +0200, Thomas Weißschuh wrote:
> > > On 2023-10-05 14:15:31-0600, Shuah Khan wrote:
> > > > Hi Thomas,
> > > > 
> > > > On 10/5/23 11:00, Thomas Weißschuh wrote:
> > > > > Hi Shuah,
> > > > > 
> > > > > I'd like to test the current state of nolibc in linux-next.
> > > > > Could pull the request below into your nolibc branch?
> > > > > 
> > > > > I'll do some manual tests this weekend, too.
> > > > > 
> > > > > 
> > > > > Thanks,
> > > > > Thomas
> > > > > 
> > > > > 
> > > > > The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
> > > > > 
> > > > >     Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
> > > > > 
> > > > > are available in the Git repository at:
> > > > > 
> > > > >     https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git nolibc/next
> > > > > 
> > > > > for you to fetch changes up to ab663cc32912914258bc8a2fbd0e753f552ee9d8:
> > > > > 
> > > > >     tools/nolibc: automatically detect necessity to use pselect6 (2023-09-28 09:20:35 +0200)
> > > > 
> > > > Absolutely. Do you mind tagging and pushing the tag and send
> > > > pull request with the tag?
> > > 
> > > Sure, here it is:
> > > 
> > > 
> > > The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
> > > 
> > >    Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
> > > 
> > > are available in the Git repository at:
> > > 
> > >    https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git nolibc-next.2023.10.05a
> > > 
> > > for you to fetch changes up to ab663cc32912914258bc8a2fbd0e753f552ee9d8:
> > > 
> > >    tools/nolibc: automatically detect necessity to use pselect6 (2023-09-28 09:20:35 +0200)
> > 
> > Looks good on my laptop:
> > 
> > make run:
> > 
> > 	160 test(s): 160 passed,   0 skipped,   0 failed => status: success
> > 
> > make run-user:
> > 
> > 	160 test(s): 158 passed,   2 skipped,   0 failed => status: warning
> > 
> > Shuah, I can take nolibc for the upcoming merge window (I believe that
> > it is my turn to do so), but if you would prefer to take them, that also
> > works for me.  Either way, just let me know.
> 
> Yes it is your turn. Please go ahead and take them.

Very good, I will merge them in and post them to the relevant email lists.

> I will pull and do testing and update you on how it went.

Looking forward to seeing what you find!

							Thanx, Paul