linux-kernel - Re: linux-next: duplicate patch in the nolibc tree

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: <e0af8d82-e099-49fa-9fbd-6f6bb63b7706@t-8ch.de>
Date:   Thu, 17 Aug 2023 18:30:54 +0200
From:   Thomas Weißschuh <thomas@...ch.de>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Shuah Khan <skhan@...uxfoundation.org>, Willy Tarreau <w@....eu>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        Christian Brauner <brauner@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the nolibc tree

On 2023-08-17 13:38:11+1000, Stephen Rothwell wrote:
> The following commit is also in the vfs-brauner tree as a different commit
> (but the same patch):
> 
>   ba859b2e419c ("selftests/nolibc: drop test chmod_net")
> 
> This is commit
> 
>   49319832de90 ("selftests/nolibc: drop test chmod_net")
> 
> in the vfs-brauner tree.

I think we can drop the patch from the nolibc tree.
The patch is only really necessary in combination with
commit 18e66ae67673 ("proc: use generic setattr() for /proc/$PID/net")
which already is and should stay in the vfs tree.