From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,surenb@google.com,mykyta.yatsenko5@gmail.com,Liam.Howlett@Oracle.com,andrii@kernel.org,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: + procfs-avoid-fetching-build-id-while-holding-vma-lock-fix.patch added to mm-nonmm-unstable branch
Date: Thu, 29 Jan 2026 13:56:49 -0800 [thread overview]
Message-ID: <20260129215650.3B361C4CEF7@smtp.kernel.org> (raw)
The patch titled
Subject: procfs-avoid-fetching-build-id-while-holding-vma-lock-fix
has been added to the -mm mm-nonmm-unstable branch. Its filename is
procfs-avoid-fetching-build-id-while-holding-vma-lock-fix.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/procfs-avoid-fetching-build-id-while-holding-vma-lock-fix.patch
This patch will later appear in the mm-nonmm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: procfs-avoid-fetching-build-id-while-holding-vma-lock-fix
Date: Thu Jan 29 01:54:41 PM PST 2026
fix kerneldoc, per Mykyta Yatsenko
Cc: Andrii Nakryiko <andrii@kernel.org>
Cc: Liam R. Howlett <Liam.Howlett@Oracle.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/buildid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/lib/buildid.c~procfs-avoid-fetching-build-id-while-holding-vma-lock-fix
+++ a/lib/buildid.c
@@ -315,7 +315,7 @@ out:
return ret;
}
-/*
+/**
* Parse build ID of ELF file mapped to vma
* @vma: vma object
* @build_id: buffer to store build id, at least BUILD_ID_SIZE long
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-add-wq_percpu-to-alloc_workqueue-users-fix.patch
mm-add-wq_percpu-to-alloc_workqueue-users-fix-fix.patch
sparc-mm-export-symbols-for-lazy_mmu_mode-kunit-tests-fix.patch
mm-vma-document-possible-vma-vm_refcnt-values-and-reference-comment-fix.patch
mm-vma-introduce-helper-struct-thread-through-exclusive-lock-fns-fix.patch
mm-pagewalk-use-min-to-simplify-the-code-fix.patch
mm-relocate-the-page-table-ceiling-and-floor-definitions-fix.patch
mm-update-shmem__file_-functions-to-use-vma_flags_t-fix.patch
procfs-avoid-fetching-build-id-while-holding-vma-lock-fix.patch
next reply other threads:[~2026-01-29 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 21:56 Andrew Morton [this message]
2026-01-29 22:12 ` + procfs-avoid-fetching-build-id-while-holding-vma-lock-fix.patch added to mm-nonmm-unstable branch 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=20260129215650.3B361C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@Oracle.com \
--cc=andrii@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mykyta.yatsenko5@gmail.com \
--cc=surenb@google.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.