From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 397C43264F2 for ; Fri, 3 Apr 2026 12:13:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=18.9.28.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775218416; cv=none; b=L8HAWOQ1XtiIV3NIOUi8ady59vc0uQwv1SK9INlb4IRhLUPpmo4u0OTDh4hmFV76TEY0wgAMwLQqUyk6s4abDHg9t6HAEzVO0diU42Y2He5MHXHLKpJkCuycC7AIFPciXQSog/rUoTWUsOVaBT3UUjTd0mzVAVdImyF90bvrzPM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775218416; c=relaxed/simple; bh=kBkwCZu869nRy5oKAkofwAyea/wE/SghKoVo2g55cfw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Toi+NJZvnWkNSNGRNc0VqA9pe+M4aZ7sqCNb9/m5hAr++XXu6FSo6WyToQvenBVY8KZsSiyuoVIaMlYVrj0va8qm8HcRF77Zul4yVpHt1n4tedwpG1D7geRvuKMWou2/IlaUk2w+NeiBAx9nJh2cV7+mRdaV4rvwho/d+oPtItU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=mit.edu; spf=pass smtp.mailfrom=mit.edu; dkim=pass (2048-bit key) header.d=mit.edu header.i=@mit.edu header.b=NNRC51tF; arc=none smtp.client-ip=18.9.28.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=mit.edu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mit.edu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mit.edu header.i=@mit.edu header.b="NNRC51tF" Received: from macsyma.thunk.org (pool-173-48-112-174.bstnma.fios.verizon.net [173.48.112.174]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 633CCVNT010933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 3 Apr 2026 08:12:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1775218355; bh=7B1eiaWm/UkTFt8XrqSb5Y7bJ+v6NouwCVV7bNYl2nc=; h=Date:From:Subject:Message-ID:MIME-Version:Content-Type; b=NNRC51tFae2L5xXUEs8gBhiZiNOYIyBm1GEm6F+R9ZKFdmZCCrpr07aLlsEqYssxc Hm5rrOR697XluAt2TK2KJLlUgP++6n/WYTOhDvhm87d2MAvyrxyp5K5tn/kPu/Edw0 JIxU3uKVP9pWZ6rDugjB8quAiySRspghP48QXwTfV0nocBFAP0Kcj3W5OIVOVlFJeb dj4XNUSJP+DXrdRnEGXm+V96W2DzSgyHnjMKa91bZvbcRm2du2MAfMbfyOqrrsQ7ZI wsAMQl6UCz4/aqOwdaM3iuKL+FWtXKQlSO59Lsl3lyh7V1B+WvGOx6ef0pIY2PKsrS Fq8ndPl2rh7MA== Received: by macsyma.thunk.org (Postfix, from userid 15806) id ED4476100637; Fri, 3 Apr 2026 08:11:30 -0400 (EDT) Date: Fri, 3 Apr 2026 08:11:30 -0400 From: "Theodore Tso" To: "Lorenzo Stoakes (Oracle)" Cc: Roman Gushchin , Sean Christopherson , linux-kernel , Andrew Morton , Guenter Roeck , Konstantin Ryabitsev , Chris Mason , SeongJae Park , elkin@google.com, Christian Brauner , Dmitry Vyukov , Sasha Levin , Shakeel Butt , Lorenzo Stoakes , Ian Rogers , Venkatesh Srinivas , Paolo Bonzini Subject: Re: Introduce Sashiko (agentic review of Linux kernel changes) Message-ID: <20260403121130.GB12260@macsyma-wired.lan> References: <7ia4o6kmpj5s.fsf@castle.c.googlers.com> <39e6b4d2-8a30-4eaa-908d-5d11b746f8d5@lucifer.local> <87v7etugwd.fsf@linux.dev> <34630bb5-840b-4a99-8e19-51fd4fc8ba96@lucifer.local> <87jyv7a1q5.fsf@linux.dev> <875x68n7a5.fsf@linux.dev> <50fa537f-65e2-4e8a-b9ab-932a22943a3a@lucifer.local> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50fa537f-65e2-4e8a-b9ab-932a22943a3a@lucifer.local> One other thing to consider is copyright. This issue is one we can safely ignore when we are asking LLM's to review code. But if ask LLM's to generate documentation, and then we cut and paste the generated text into kernel documentation, the copyright status of the generated text is not well defined. In Europe, the European Comission has promulgated that LLM output, having been generated by a machine, and not a human being, is not copyrighted. If a human being then makes changes, the combined work could be subject to copyright, and if it is merged into code that is subject to the GPL (for example), the combined work would also be subject to the original license. But that's only in Europe. But consider researchers were able to extract 96% of Harry Potter and the Sourcerer's Stone from Claude 3.7 Sonnet. So with the right prompt, if we get a paragraph that came from some published book about Linux, and it was dropped into the Documentation/ directory, that might be problematic, since even (or maybe especially) the European Union might want to take a hard line. (Do you hear the people sing, singing the songs of angry Victor Hugo's? :-) If we use an LLM model analyze docuemntation to identify gaps, and we take a bullet list of missing functions or semantics, and the human being writes new text from scratch, instead of cutting and pasting directly from LLM, that should be safe. But of course, I'm not a lawyer and I don't play one on TV. Cheers, - Ted