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>] [day] [month] [year] [list]
Message-ID: <20250703125121.2f34c015@canb.auug.org.au>
Date: Thu, 3 Jul 2025 12:51:21 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Daniel Borkmann <daniel@...earbox.net>, Alexei Starovoitov
 <ast@...nel.org>, Andrii Nakryiko <andrii@...nel.org>, Christian Brauner
 <brauner@...nel.org>
Cc: bpf <bpf@...r.kernel.org>, Networking <netdev@...r.kernel.org>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: linux-next: duplicate patches in the bpf-next tree

Hi all,

The following commits are also in the vfs-brauner tree as different
commits (but the same patches):

  f4fba2d6d282 ("selftests/bpf: Add tests for bpf_cgroup_read_xattr")
  1504d8c7c702 ("bpf: Mark cgroup_subsys_state->cgroup RCU safe")
  535b070f4a80 ("bpf: Introduce bpf_cgroup_read_xattr to read xattr of cgroup's node")

These are commits

  21eebc655b0f ("selftests/bpf: Add tests for bpf_cgroup_read_xattr")
  5bc9557c9f17 ("bpf: Mark cgroup_subsys_state->cgroup RCU safe")
  b95ee9049c93 ("bpf: Introduce bpf_cgroup_read_xattr to read xattr of cgroup's node")

in the vfs-brauner tree.

These duplicates are causing unnecessary conflicts.

The previous commit in both trees is not quite identical.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ