Re: linux-next: test failure after merge of the landlock tree

["Mickaël Salaün" <mic@digikod.net>]

On Tue, Oct 20, 2026 at 02:33:26PM +0100, Mark Brown wrote:
> On Tue, Oct 20, 2026 at 03:16:51PM +0200, Mickaël Salaün wrote:
> > On Tue, Oct 20, 2026 at 02:02:42PM +0100, Mark Brown wrote:
> 
> > > What I have today is f349c073889ff7694b470ca34dae9bd94d47b0cc which is
> > > "landlock: Fix superblock use-after-free in release_inode()" rebased on
> > > the 16th (I just tried refetching and there was no change).  It seems
> > > very surprising that there might have been an infrastructure issue
> > > fetching the tree all of Thursday, Friday and Monday?
> 
> > Commit 0da3cb3db77e3fe2202ddb637f6d27668dc360f7 appears in the
> > transparency log:
> > https://git.kernel.org/pub/scm/infra/transparency-logs/gitolite/git/1.git/commit/?id=0da8a8d3dc37ec9a71b76f9739957297d64d4b73
> 
> This probably needs reporting to helpdesk (CCed), when I fetch:
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git next
> 
> or go to:
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git/commit/?id=f349c073889ff7694b470ca34dae9bd94d47b0cc
> 
> what I see is the commit referenced above being the head of your next
> branch, not this other one you are mentioning.  I'm on the fra mirror.

This head commit correct.  I mean that commit 0da3cb3db77e ("landlock:
Enforce capability restrictions") was the one that fixed the kunit issue
and it was part of the commits I pushed Wednesday.  Anyway, it looks
good now, thanks.