From: Andrew Morton <akpm@linux-foundation.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
linux-mm@vger.kernel.org, linux-fsdevel@vger.kernel.org,
bpf@vger.kernel.org, surenb@google.com,
syzbot+4e70c8e0a2017b432f7a@syzkaller.appspotmail.com
Subject: Re: [PATCH mm-stable] procfs: avoid fetching build ID while holding VMA lock
Date: Thu, 29 Jan 2026 15:28:42 -0800 [thread overview]
Message-ID: <20260129152842.b8db6be6aa9e4fa93e69cc5b@linux-foundation.org> (raw)
In-Reply-To: <CAEf4BzZJSuc0AH1Hio-DVpgR9S-KZsMNqU7tb--c4=mPZJ5dcA@mail.gmail.com>
On Wed, 28 Jan 2026 13:30:37 -0800 Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
> > To provide for additional review and test time I'll queue the fix for
> > the upcoming merge window (Feb 18 upstream merge) with a cc:stable.
>
> This seems to be exacerbated (as we haven't seen these syzbot reports
> before that) by more recent:
>
> 777a8560fd29 ("lib/buildid: use __kernel_read() for sleepable context")
>
> which is in mm-stable. So I'm not sure, probably would be best to have
> both of them together.
777a8560fd29 is actually in mainline. I'll move this fix into mm.git's
mm-hotfixes queue so it should be present in 6.19.
next prev parent reply other threads:[~2026-01-29 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 18:32 [PATCH mm-stable] procfs: avoid fetching build ID while holding VMA lock Andrii Nakryiko
2026-01-28 18:50 ` Andrew Morton
2026-01-28 21:30 ` Andrii Nakryiko
2026-01-29 23:28 ` Andrew Morton [this message]
2026-01-29 5:50 ` Suren Baghdasaryan
2026-01-29 21:43 ` Andrii Nakryiko
2026-01-29 15:52 ` Yonghong Song
2026-01-29 17:14 ` Mykyta Yatsenko
2026-01-29 21:46 ` Andrii Nakryiko
2026-01-29 21:48 ` Andrii Nakryiko
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=20260129152842.b8db6be6aa9e4fa93e69cc5b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=surenb@google.com \
--cc=syzbot+4e70c8e0a2017b432f7a@syzkaller.appspotmail.com \
/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.