Patch Series

Subject	docs/mm: explain when and why rmap locks need to be taken during mremap()
Author	harry.yoo@oracle.com
Date	2025-08-26 06:58:47 +0000 UTC
Version	1
Cc	akpm@linux-foundation.org corbet@lwn.net david@redhat.com harry.yoo@oracle.com jannh@google.com kees@kernel.org liam.howlett@oracle.com linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com mhocko@suse.com pfalcato@suse.de riel@surriel.com rppt@kernel.org shakeel.butt@linux.dev surenb@google.com vbabka@suse.cz

Patches (2)

Name	Content
[PATCH V1 1/2] docs/mm: explain when and why rmap locks need to be taken during mremap()	[Body]
[PATCH V1 2/2] mm: document when rmap locks can be skipped when setting need_rmap_locks	[Body]

Session 2025-08-26

ID (for dev)	4b3b105a-2c48-4057-8974-da8175654b9f
Status	finished
Triaged	OK [Log]
Execution Log	[Link]

Test	Base	Patched	Verdict
Build Base	068a56e56fa81e42fc5f08dff34fab149bb60a09 [Config]		passed [Log]
Build Patched		068a56e56fa81e42fc5f08dff34fab149bb60a09 [Config] [patched]	passed [Log]
Boot test: Base	068a56e56fa81e42fc5f08dff34fab149bb60a09 [Config]		passed
Boot test: Patched		068a56e56fa81e42fc5f08dff34fab149bb60a09 [Config] [patched]	passed
Fuzzing	068a56e56fa81e42fc5f08dff34fab149bb60a09 [Config]	068a56e56fa81e42fc5f08dff34fab149bb60a09 [Config] [patched]	passed [Log] [Artifacts]