From: "Luck, Tony" <tony.luck@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Mike Rapoport <rppt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Christian Brauner <brauner@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Theodore Ts'o <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, Kees Cook <kees@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: RE: [PATCH] [v2] Documentation: Provide guidelines for tool-generated content
Date: Mon, 10 Nov 2025 21:52:34 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083B928B445DF82EE5AE3EEFCCEA@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20251110164225.4b343fe4@gandalf.local.home>
> I believe that's what is currently being argued in court. If AI is trained
> on human content and prints out something based on it, is it a non-human
> creation? This isn't a case of a monkey taking a selfie, where the content
> provider is clearly non-human. This is a machine that uses human created
> content to derive new creations.
If the output were deemed copyrightable, who should own that copyright?
Option 1 is "The human that crafted the prompt to generate it"
Option 2 is "The corporation that spent vast resources to create that AI model"
Option 3 is "The owners of the copyrighted material used to train the AI".
If a court ever must decide which to pick, it may well pick the answer requested
by the best funded legal team (which would be option 2).
-Tony
next prev parent reply other threads:[~2025-11-10 21:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251105231514.3167738-1-dave.hansen@linux.intel.com>
2025-11-10 7:43 ` Vlastimil Babka
2025-11-10 8:58 ` Christian Brauner
2025-11-10 16:08 ` Dave Hansen
2025-11-10 17:25 ` Laurent Pinchart
2025-11-10 17:41 ` Dave Hansen
2025-11-10 17:44 ` Linus Torvalds
2025-11-10 17:56 ` Luck, Tony
2025-11-10 18:39 ` Mike Rapoport
2025-11-10 19:05 ` Linus Torvalds
2025-11-10 19:18 ` H. Peter Anvin
2025-11-10 19:36 ` Linus Torvalds
2025-11-10 19:54 ` Steven Rostedt
2025-11-10 20:00 ` Konstantin Ryabitsev
2025-11-10 20:25 ` Steven Rostedt
2025-11-10 21:21 ` James Bottomley
2025-11-10 21:42 ` Steven Rostedt
2025-11-10 21:52 ` Luck, Tony [this message]
2025-11-10 22:07 ` James Bottomley
2025-11-10 23:16 ` Theodore Ts'o
2025-11-11 9:35 ` Lorenzo Stoakes
2025-11-11 13:08 ` Theodore Ts'o
2025-11-10 17:46 ` Steven Rostedt
[not found] ` <11eaf7fa-27d0-4a57-abf0-5f24c918966c@lucifer.local>
2025-11-10 11:15 ` Lorenzo Stoakes
[not found] ` <103ee61c-f958-440c-af73-1cf3600d10fd@intel.com>
2025-11-10 16:51 ` Lorenzo Stoakes
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=SJ1PR11MB6083B928B445DF82EE5AE3EEFCCEA@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=workflows@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox