linux-kernel - linux-next: manual merge of the kspp tree with Linus' 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]

Message-ID: <20240709175803.36f8bca6@canb.auug.org.au>
Date: Tue, 9 Jul 2024 17:58:03 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kees Cook <kees@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, liujinlong <liujinlong@...inos.cn>,
 liujinlong <mingliu6104@...il.com>
Subject: linux-next: manual merge of the kspp tree with Linus' tree

Hi all,

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

  kernel/kallsyms.c

between commit:

  7e1f4eb9a60d ("kallsyms: rework symbol lookup return codes")

from Linus' tree and commit:

  21b4564fedad ("sprint_symbol: Replace strcpy with memmove to handle potential overlap")

from the kspp tree.

I fixed it up (the former removed the code modified by the latter, so I
did that) 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.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped