From: "Mickaël Salaün" <mic@digikod.net>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: test failure after merge of the landlock tree
Date: Tue, 20 Oct 2026 15:16:51 +0200 [thread overview]
Message-ID: <20261020.shai5aMoosai@digikod.net> (raw)
In-Reply-To: <atdmcnGhgZ9U8g_S@sirena.co.uk>
On Tue, Oct 20, 2026 at 02:02:42PM +0100, Mark Brown wrote:
> On Tue, Oct 20, 2026 at 02:28:48PM +0200, Mickaël Salaün wrote:
> > On Tue, Oct 20, 2026 at 10:54:29AM +0100, Mark Brown wrote:
>
> > > > I removed these wrong kunit checks Friday so it should be good now, but
>
> > In fact, I updated mic/next Wednesday with a new patch series addressing
> > these issues. I only added two (unrelated) commits on top of that
> > Friday.
>
> 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
next prev parent reply other threads:[~2026-10-20 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 0:31 linux-next: test failure after merge of the landlock tree Mark Brown
2026-10-19 18:17 ` Mark Brown
2026-10-19 21:11 ` Mickaël Salaün
2026-10-20 9:54 ` Mark Brown
2026-10-20 12:28 ` Mickaël Salaün
2026-10-20 13:02 ` Mark Brown
2026-10-20 13:16 ` Mickaël Salaün [this message]
2026-10-20 13:33 ` Mark Brown
2026-10-20 13:47 ` Mickaël Salaün
2026-10-20 13:46 ` Mark Brown
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=20261020.shai5aMoosai@digikod.net \
--to=mic@digikod.net \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.