From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH v2] mm/vma: keep the unlinked VMA off the file across unmap on mmap hook failure
Date: Fri, 9 Oct 2026 09:38:56 -0700 [thread overview]
Message-ID: <271f7ba8-df38-4c8f-b59d-68b52ee998e9@linux.dev> (raw)
In-Reply-To: <asjQQF_Ok1TZPm1M@gremlin>
On 2026-10-09 4:31 a.m., Lorenzo Stoakes (ARM) wrote:
> -cc slopper
>
> On Thu, Oct 08, 2026 at 02:48:07PM -0700, Ihor Solodrai wrote:
>> BPF CI caught this bug on linux-next as well:
>> https://github.com/kernel-patches/bpf/actions/runs/37736351874
>
> Nice that it caught it!
>
> Is there a way to automatically notify patch author that when it happens? Does
> it bisect, etc. or just green/red?
For linux-next it's just green/red now.
We've added it to have an "upstream merge will break bpf" signal,
because it happened regularly.
For bpf list we run on every incoming patch, so regressions are detected
quickly. Not feasible to do that for *every* upstream patch, we'd need
much more compute.
An auto-bisection is something I thought about, but never got to it.
These days with LLMs this may be easier to set up though.
>
> --
> Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-09 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261007101800.58d50b1b20a10738e630bfd5@linux-foundation.org>
[not found] ` <20261007194708.2009-1-okerixx@gmail.com>
2026-10-08 21:48 ` [PATCH v2] mm/vma: keep the unlinked VMA off the file across unmap on mmap hook failure Ihor Solodrai
2026-10-09 11:31 ` Lorenzo Stoakes (ARM)
2026-10-09 16:38 ` Ihor Solodrai [this message]
2026-10-09 17:04 ` Lorenzo Stoakes (ARM)
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=271f7ba8-df38-4c8f-b59d-68b52ee998e9@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox