From: Jakub Acs <acsjakub@amazon.de>
To: <linux-mm@kvack.org>
Cc: <acsjakub@amazon.de>, <akpm@linux-foundation.org>,
<david@redhat.com>, <xu.xin16@zte.com.cn>,
<chengming.zhou@linux.dev>, <peterx@redhat.com>,
<axelrasmussen@google.com>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/2] mm, ksm: fix flag-dropping behavior
Date: Wed, 1 Oct 2025 09:03:51 +0000 [thread overview]
Message-ID: <20251001090353.57523-1-acsjakub@amazon.de> (raw)
Hi,
This series fixes a bug in ksm_madvise described in [1/2].
As asked by David in the reply to v2, I separated the change into two
commits:
- first contains minimal fix for the bug to make it
individually-backportable
- second makes the VM_* flag definitions consistent
v1: https://lore.kernel.org/all/20250930063921.62354-1-acsjakub@amazon.de/
v2: https://lore.kernel.org/all/20250930130023.60106-1-acsjakub@amazon.de/
Jakub Acs (2):
mm/ksm: fix flag-dropping behavior in ksm_madvise
mm: redefine VM_* flag constants with BIT()
include/linux/mm.h | 68 +++++++++++++++++++++++-----------------------
1 file changed, 34 insertions(+), 34 deletions(-)
--
2.47.3
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10243 Berlin
Geschaeftsfuehrung: Christian Schlaeger
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next reply other threads:[~2025-10-01 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 9:03 Jakub Acs [this message]
2025-10-01 9:03 ` [PATCH v3 1/2] mm/ksm: fix flag-dropping behavior in ksm_madvise Jakub Acs
2025-10-01 14:06 ` David Hildenbrand
2025-10-01 16:43 ` SeongJae Park
2025-11-06 10:39 ` Vlastimil Babka
2025-11-06 11:16 ` David Hildenbrand (Red Hat)
2025-11-07 9:49 ` Jakub Acs
2025-11-10 10:00 ` Vlastimil Babka
2025-10-01 9:03 ` [PATCH v3 2/2] mm: redefine VM_* flag constants with BIT() Jakub Acs
2025-10-01 14:04 ` David Hildenbrand
2025-10-02 8:03 ` Jakub Acs
2025-10-01 16:51 ` SeongJae Park
2025-10-02 7:29 ` David Hildenbrand
2025-10-02 17:39 ` SeongJae Park
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=20251001090353.57523-1-acsjakub@amazon.de \
--to=acsjakub@amazon.de \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=xu.xin16@zte.com.cn \
/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