linux-kernel - Re: linux-next: duplicate patch in the vfs-brauner 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: <20250708-zocken-funkanstalt-9e658ddeca5c@brauner>
Date: Tue, 8 Jul 2025 10:35:31 +0200
From: Christian Brauner <brauner@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: 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 vfs-brauner tree

On Tue, Jul 08, 2025 at 09:51:18AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the vfs-brauner-fixes tree as a different
> commit (but the same patch):
> 
>   8c0bcafc722c ("coredump: fix PIDFD_INFO_COREDUMP ioctl check")
> 
> This is commit
> 
>   830a9e37cfb2 ("coredump: fix PIDFD_INFO_COREDUMP ioctl check")
> 
> in te vfs-brauner-fixes tree.

Interesting. Are you merging vfs.fixes separately? Fwiw, I always merge
vfs.fixes into vfs.all. So if it's easier for you you can drop merging
vfs.fixes separately.

Christian