linux-kernel - Re: [PATCH 09/10] drivers/auxdisplay: add a KFuzzTest for parse

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: <2025120431-squishier-cold-8cde@gregkh>
Date: Thu, 4 Dec 2025 16:56:01 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Marco Elver <elver@...gle.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
	Ethan Graham <ethan.w.s.graham@...il.com>, glider@...gle.com,
	andreyknvl@...il.com, andy@...nel.org, brauner@...nel.org,
	brendan.higgins@...ux.dev, davem@...emloft.net, davidgow@...gle.com,
	dhowells@...hat.com, dvyukov@...gle.com,
	herbert@...dor.apana.org.au, ignat@...udflare.com, jack@...e.cz,
	jannh@...gle.com, johannes@...solutions.net,
	kasan-dev@...glegroups.com, kees@...nel.org,
	kunit-dev@...glegroups.com, linux-crypto@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, lukas@...ner.de,
	shuah@...nel.org, sj@...nel.org, tarasmadan@...gle.com
Subject: Re: [PATCH 09/10] drivers/auxdisplay: add a KFuzzTest for parse_xy()

On Thu, Dec 04, 2025 at 04:42:37PM +0100, Marco Elver wrote:
> On Thu, 4 Dec 2025 at 16:35, Marco Elver <elver@...gle.com> wrote:
> > On Thu, 4 Dec 2025 at 16:34, Andy Shevchenko <andy.shevchenko@...il.com> wrote:
> > >
> > > On Thu, Dec 4, 2025 at 5:33 PM Marco Elver <elver@...gle.com> wrote:
> > > > On Thu, 4 Dec 2025 at 16:26, Andy Shevchenko <andy.shevchenko@...il.com> wrote:
> > >
> > > [..]
> > >
> > > > > > Signed-off-by: Ethan Graham <ethangraham@...gle.com>
> > > > > > Signed-off-by: Ethan Graham <ethan.w.s.graham@...il.com>
> > > > >
> > > > > I believe one of two SoBs is enough.
> > > >
> > > > Per my interpretation of
> > > > https://docs.kernel.org/process/submitting-patches.html#developer-s-certificate-of-origin-1-1
> > > > it's required where the affiliation/identity of the author has
> > > > changed; it's as if another developer picked up the series and
> > > > continues improving it.
> > >
> > > Since the original address does not exist, the Originally-by: or free
> > > text in the commit message / cover letter should be enough.
> >
> > The original copyright still applies, and the SOB captures that.
> 
> +Cc Greg - who might be able to shed a light on tricky cases like this.
> 
> tldr; Ethan left Google, but continues to develop series in personal
> capacity. Question about double-SOB requirement above.

It's the same natural person, so only 1 is needed.

thanks,

greg k-h