linux-kernel - Re: 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-prev] [day] [month] [year] [list]

Message-ID: <202407090855.2CA07B977F@keescook>
Date: Tue, 9 Jul 2024 08:55:30 -0700
From: Kees Cook <kees@...nel.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-next <linux-next@...r.kernel.org>,
	liujinlong <liujinlong@...inos.cn>,
	liujinlong <mingliu6104@...il.com>
Subject: Re: linux-next: manual merge of the kspp tree with Linus' tree

On Tue, Jul 09, 2024 at 10:29:19AM +0200, Arnd Bergmann wrote:
> On Tue, Jul 9, 2024, at 09:58, Stephen Rothwell wrote:
> > 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.
> 
> Hi Stephen,
> 
> Thanks for pointing this out. It does look like the second
> patch also just tries to address the same warning that I
> fixed in my larger patch.
> 
> Kees, do you want to just drop that patch from your tree?

Yup! Done. Thanks for the larger fix! :)

-- 
Kees Cook