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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAHk-=wgPRijTr7fZQNs9pxbhRLBVQGdE7ceZDwQFP53MXjRBxg@mail.gmail.com>
Date: Thu, 15 Jan 2026 15:09:34 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Mickaël Salaün <mic@...ikod.net>
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, 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.

            Linus