From: Nils Hartmann <nils1hartmann@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Using MAP_SHARE_VALIDATE in mmap without fd
Date: Thu, 16 Mar 2023 20:16:29 +0100 [thread overview]
Message-ID: <20230316191629.2pet2mq5bpxl3z4p@archlinux> (raw)
In-Reply-To: <e6b72d88-3011-c284-f53a-71431065b991@redhat.com>
On Thu, Mar 16, 2023 at 04:28:21PM +0100, David Hildenbrand wrote:
> On 10.03.23 18:16, Nils Hartmann wrote:
> > Hey,
> > When used without a file pointer, EINVAL is returned. Is there a reason for this?
>
> You mean, using it with shared anonymous memory? (MAP_SHARED|MAP_ANON)
> I assume you mean "file descriptor" not "file pointer".
Yup thats what I meant.
> The only reason MAP_SHARED_VALIDATE was introduced was due to MAP_SYNC, only
> required for DAX. DAX does not apply to shared anonymous memory.
Yeah I heard about it being introduced with MAP_SYNC.
But since the manpage from mmap specifically says:
'MAP_SHARED_VALIDATE provides the same behaviour as MAP_SHARED',
I didn't think it would make a difference
> I guess nobody cared/cares.
> Question is if we want to update the implementation (there has to be a good
> reason IMHO) or simply update the man page, stating that MAP_SHARED_VALIDATE
> is not supported for MAP_ANON.
The only reason I can come up with, is naming consistency.
But it's really a non-issue und updating the man page is definitly
the saner option.
> --
> Thanks,
>
> David / dhildenb
>
Best Regards,
Nils
prev parent reply other threads:[~2023-03-16 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:16 Nils Hartmann
2023-03-16 15:28 ` David Hildenbrand
2023-03-16 19:16 ` Nils Hartmann [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=20230316191629.2pet2mq5bpxl3z4p@archlinux \
--to=nils1hartmann@gmail.com \
--cc=20230310171617.wqnqs42l2viwjsz5@archlinux.kvack.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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