linux-kernel - Re: [GIT PULL] Landlock fix for v6.19-rc6

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260116.feegh2ohQuae@digikod.net>
Date: Fri, 16 Jan 2026 15:18:15 +0100
From: Mickaël Salaün <mic@...ikod.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Günther Noack <gnoack@...gle.com>, 
	Matthieu Buffet <matthieu@...fet.re>, Tingmao Wang <m@...wtm.org>, linux-kernel@...r.kernel.org, 
	linux-security-module@...r.kernel.org
Subject: Re: [GIT PULL] Landlock fix for v6.19-rc6

On Thu, Jan 15, 2026 at 03:09:34PM -0800, Linus Torvalds wrote:
> On Thu, 15 Jan 2026 at 13:47, Mickaël Salaün <mic@...ikod.net> wrote:
> >
> > This PR fixes TCP handling, tests, documentation, non-audit elided code,
> > and minor cosmetic changes.
> 
> This seems significantly bigger than what you sent for the whole merge
> window for the Landlock code.
> 
> The merge window pull was - ignoring tests - 4 files changed, 59
> insertions(+), 17 deletions(-).
> 
> I want more explanations for why I'm suddenly getting more alleged
> fixes than I got any development and why this shouldn't wait until the
> next merge window.
> 
> Because honestly, this just all seems out of place.

There are indeed relatively more line changes because the related
commits are fixes for different kernel versions, not specifically v6.19
but also v6.15 (type issue), v6.7 (TCP fix), and it required to move a
lot of lines (including a lot of comments) for a theoretically small
fix.  In fact, the last merge window pull was mostly about fixes too
(which were on time for the merge window, but otherwise I would have
sent them as this one).

The other commits are documentation/comment fixes (including another
chunk of moved lines, which appears as kernel code diff), tests fixes or
minor cleanup.  I can postpone these commits but because they don't
directly impact the kernel, I wanted to group all fixes and minor
non-kernel changes together to have a clean PR for the next merge
window.  Please let me know what you prefer.

 Mickaël