All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Dan Carpenter <error27@gmail.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>, Sasha Levin <sashal@kernel.org>,
	ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc
Date: Fri, 17 Jul 2026 21:13:48 -0400	[thread overview]
Message-ID: <alrIyYVSN-kReQQU@mit.edu> (raw)
In-Reply-To: <48472b6d7c4803c5bf76235e4a8f5f9f69fcd047.camel@HansenPartnership.com>

On Fri, Jul 17, 2026 at 02:42:09PM -0500, James Bottomley wrote:
> They're not really enforced at all.  It's the legal equivalent of a
> representation, it just means I read the DCO and I represent I conform
> to what it says.  Externally we have no verification mechanism that the
> person signing off actually did this ... although if they're regular
> contributors the trust factor is higher, and if they get caught faking
> signoffs then the trust factor goes down.

This is something that perhaps we should ask legal council.  The DCO
states (among other things):

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or ...

Given, however, that we don't know whether it might mean that
vis-a-vis code which is generated by AI, we might want to ask
competent legal counsel questions such as:

1) Should we change the DCO to require disclosure if the code
was generated by an LLM?

2) If so, what detail is needed?  Does it matter, or potentially
matter, what model(s) was used to generate the code?

3) Does it matter, or potentially matter, whether the LLM was used to
generate code out of whole cloth, or to fix existing code?  For
example, if the LLM inserts a spin_unlock() call, or modifies the
prexisting code to add a scoped guard to avoid a memory leak, the
chances that this might have copyright implication might be different
compared if the LLM is asked to generate a new device driver for some
graphics card.

4) Does the prompt or series of prompts that were used matter, or
potentially matter?  If so, do we need to record them in the git
commit description, much like we sometimes include the coccinelle
script?

					- Ted

  reply	other threads:[~2026-07-18  1:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 15:09 [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc Jonathan Corbet
2026-07-16 15:28 ` Sasha Levin
2026-07-16 16:08   ` Mark Brown
2026-07-16 16:24     ` Sasha Levin
2026-07-16 20:38       ` Laurent Pinchart
2026-07-17 14:09         ` Sasha Levin
2026-07-17 14:25       ` Mark Brown
2026-07-16 18:36   ` Jonathan Corbet
2026-07-16 19:53     ` Mauro Carvalho Chehab
2026-07-16 23:59       ` Theodore Tso
2026-07-17  0:58         ` Mauro Carvalho Chehab
2026-07-17  2:27           ` Theodore Tso
2026-07-17  7:19             ` Mauro Carvalho Chehab
2026-07-17 13:55         ` Konstantin Ryabitsev
2026-07-17 14:24           ` Andrew Lunn
2026-07-17 14:32             ` Konstantin Ryabitsev
2026-07-17 14:50               ` Andrew Lunn
2026-07-17 20:21           ` Theodore Tso
2026-07-16 20:05     ` Bart Van Assche
2026-07-16 20:52       ` James Bottomley
2026-07-16 20:23     ` Liam R. Howlett
2026-07-17  7:49       ` Laurent Pinchart
2026-07-17 15:55         ` Liam R. Howlett
2026-07-17 11:57       ` James Bottomley
2026-07-17 15:53         ` Liam R. Howlett
2026-07-17 18:12           ` James Bottomley
2026-07-17 18:27             ` Dan Carpenter
2026-07-17 18:42               ` James Bottomley
2026-07-18  1:13                 ` Theodore Tso [this message]
2026-07-18  3:07                   ` James Bottomley
2026-07-17 14:54       ` Johannes Weiner
2026-07-17 16:09         ` Liam R. Howlett
2026-07-16 21:23     ` Theodore Tso
2026-07-17 13:59     ` Sasha Levin
2026-07-17 14:09       ` Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alrIyYVSN-kReQQU@mit.edu \
    --to=tytso@mit.edu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=corbet@lwn.net \
    --cc=error27@gmail.com \
    --cc=ksummit@lists.linux.dev \
    --cc=liam@infradead.org \
    --cc=sashal@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.