linux-kernel - linux-next: manual merge of the tomoyo tree with the net-next 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-next>] [day] [month] [year] [list]

Date: Tue, 11 Jun 2024 11:20:46 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, David Miller
 <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
 <pabeni@...hat.com>, Networking <netdev@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the tomoyo tree with the net-next tree

Hi all,

Today's linux-next merge of the tomoyo tree got a conflict in:

  net/netlink/af_netlink.c

between commits:

  5380d64f8d76 ("rtnetlink: move rtnl_lock handling out of af_netlink")
  5fbf57a937f4 ("net: netlink: remove the cb_mutex "injection" from netlink core")

from the net-next tree and commit:

  c2bfadd666b5 ("rtnetlink: print rtnl_mutex holder/waiter for debug purpose")

from the tomoyo tree.

I fixed it up (I just used the former) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

It looks like the tomoyo tree commit should just be completely dropped?
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped