From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
wangfushuai <wangfushuai@baidu.com>
Cc: andrii@kernel.org, osalvador@suse.de, Liam.Howlett@Oracle.com,
christophe.leroy@csgroup.eu, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] /proc/pid/smaps: add mo info for vma in NOMMU system
Date: Tue, 10 Jun 2025 13:15:23 +0200 [thread overview]
Message-ID: <c08c2f5f-2607-42d3-8d68-4ea99c2d7e72@redhat.com> (raw)
In-Reply-To: <20250607141857.40b912e164b8211b6d62eafd@linux-foundation.org>
On 07.06.25 23:18, Andrew Morton wrote:
> On Sun, 8 Jun 2025 00:53:35 +0800 wangfushuai <wangfushuai@baidu.com> wrote:
>
>> Add mo in /proc/[pid]/smaps to indicate vma is marked VM_MAYOVERLAY,
>> which means the file mapping may overlay in NOMMU system.
>>
>> ...
>>
>> Fixes: b6b7a8faf05c ("mm/nommu: don't use VM_MAYSHARE for MAP_PRIVATE mappings")
>
> In what sense does this "fix" b6b7a8faf05c? Which, after all, said "no
> functional change intended".
>
> It does appear to be an improvement to the NOMMU user interface.
> However it is non-backward-compatible - perhaps there's existing
> userspace which is looking for "um" and which now needs to be changed
> to look for "mo".
Very likely no. Nobody should be caring about this kernel-internal thing.
But let's read the doc:
"Note that there is no guarantee that every flag and associated mnemonic
will be present in all further kernel releases. Things get changed, the
flags may be vanished or the reverse -- new added. Interpretation of
their meaning might change in future as well. So each consumer of these
flags has to follow each specific kernel version for the exact semantic."
So nobody should be relying on any of that, but the doc goes on
"
This file is only present if the CONFIG_MMU kernel configuration option
is enabled.
"
Huh?
$ grep "task_mmu" fs/proc/Makefile
CFLAGS_task_mmu.o += -Wno-override-init
proc-$(CONFIG_MMU) := task_mmu.o
NAK
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-06-10 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 16:53 wangfushuai
2025-06-07 17:58 ` David Hildenbrand
2025-06-07 21:18 ` Andrew Morton
2025-06-10 11:15 ` David Hildenbrand [this message]
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=c08c2f5f-2607-42d3-8d68-4ea99c2d7e72@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=wangfushuai@baidu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®