From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Pedro Falcato <pfalcato@suse.de>, Yibin Liu <liuyibin@hygon.cn>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Liam.Howlett@oracle.com, viro@zeniv.linux.org.uk,
brauner@kernel.org, mjguzik@gmail.com, wujianyong@hygon.cn,
huangsj@hygon.cn, zhongyuan@hygon.cn
Subject: Re: [PATCH] mm: Add RWH_RMAP_EXCLUDE flag to exclude files from rmap sharing
Date: Wed, 22 Apr 2026 09:19:16 +0200 [thread overview]
Message-ID: <272e2d8b-56b6-4d60-9daa-6743c2fa7209@kernel.org> (raw)
In-Reply-To: <rbc5ezm4uuzbcfaah6w6em6ndfbhamiug5jmp6srovqsx7u2zv@nvyvigon4hcw>
>> @@ -72,6 +72,7 @@
>> #define RWH_WRITE_LIFE_MEDIUM 3
>> #define RWH_WRITE_LIFE_LONG 4
>> #define RWH_WRITE_LIFE_EXTREME 5
>> +#define RWH_RMAP_EXCLUDE 6
>
> Userspace does not know what "rmap" is, nor does it need to know. Even if you
> found a workable solution for the permission side, this is not a good solution,
> and it's not a good interface.
It's horrible and I am surprised this patch is not tagged as RFC :)
--
Cheers,
David
next prev parent reply other threads:[~2026-04-22 7:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 2:09 [PATCH] mm: Add RWH_RMAP_EXCLUDE flag to exclude files from rmap sharing Yibin Liu
2026-04-21 14:38 ` Matthew Wilcox
2026-04-21 15:37 ` Pedro Falcato
2026-04-22 7:19 ` David Hildenbrand (Arm) [this message]
2026-04-21 19:46 ` Mateusz Guzik
2026-04-22 13:03 ` 答复: " Yibin Liu
2026-04-22 10:49 ` Lorenzo Stoakes
2026-04-22 12:51 ` 答复: " Yibin Liu
2026-04-22 16:16 ` Lorenzo Stoakes
2026-04-24 1:08 ` 答复: " Yibin Liu
2026-04-24 3:20 ` Matthew Wilcox
2026-04-24 6:20 ` Mateusz Guzik
2026-04-24 6:54 ` Mateusz Guzik
-- strict thread matches above, loose matches on Subject: below --
2026-05-01 6:26 kernel test robot
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=272e2d8b-56b6-4d60-9daa-6743c2fa7209@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=huangsj@hygon.cn \
--cc=linux-mm@kvack.org \
--cc=liuyibin@hygon.cn \
--cc=mjguzik@gmail.com \
--cc=pfalcato@suse.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wujianyong@hygon.cn \
--cc=zhongyuan@hygon.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 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.