From: "Michael Kerrisk (man-opages)" <mtk.manpages@gmail.com>
To: Yubin Ruan <ablacktshirt@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
linux-mm@kvack.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH] shmat(2) returns page size aligned memory address
Date: Mon, 9 Oct 2017 10:28:24 +0200 [thread overview]
Message-ID: <3f1e2110-e736-0f53-c8a6-12bfcda433f7@gmail.com> (raw)
In-Reply-To: <20171009092251.GC5758@HP>
Thanks, Yubin. Patch applied.
Cheers,
Michael
On 10/09/2017 04:27 PM, Yubin Ruan wrote:
> On Sun, Oct 08, 2017 at 11:37:05PM +0800, Yubin Ruan wrote:
>> Hi Michael,
>> At the current man page for shmat(2)[1], there is no mentioning
>> whether the returned memory address of shmat(2) will be page size
>> aligned or not. As that is quite important to many applications(e.g.,
>> those that use locks heavily and would like to avoid some locks by
>> some atomic guarantees provided by the CPU), it would be great to
>> specify that for Linux.
>>
>> I walked down the current implementation of shmat(2) in the latest
>> kernel src and found that shmat(2) does return a page size aligned
>> memory address:
>>
>> SYSCALL_DEFINE3(shmat, int, shmid, char __user *, shmaddr, int, shmflg)
>> -> do_shmat(...)
>> -> do_mmap_pgoff(...)
>> -> do_mmap(...)
>> -> get_unmapped_area(...)
>> -> get_area(...) -> offset_in_page(addr)
>>
>> there is a `offset_in_page(addr)' assertion at the end and if that is
>> true a -EINVAL would be returned, by which we can be sure that
>> shmat(2) will return a page size aligned memory address on success[2].
>>
>> I will create a patch later if that is acceptable.
>>
>> Thanks,
>> Yubin
>>
>> [1]: http://man7.org/linux/man-pages/man2/shmat.2.html
>> [2]: there is also a `offset_in_page(2)' in get_unmapped_area(...),
>> but that doesn't lead to -EINVAL...I am not sure whether the logic of
>> that code is right.
>
> add the page-alignment attribute of the return address of shmat(2)
> ---
>
> diff --git a/man2/shmop.2 b/man2/shmop.2
> index 849529f..b8d7595 100644
> --- a/man2/shmop.2
> +++ b/man2/shmop.2
> @@ -63,7 +63,7 @@ with one of the following criteria:
> If
> .I shmaddr
> is NULL,
> -the system chooses a suitable (unused) address at which to attach
> +the system chooses a suitable (unused) page-aligned address to attach
> the segment.
> .IP *
> If
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-10-09 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJYFCiPhNVCMRVD-QpwsZk0wAKRXzFWcwVZDqLXxsxYfhFcVpg@mail.gmail.com>
2017-10-08 15:39 ` Yubin Ruan
2017-10-09 14:27 ` [PATCH] " Yubin Ruan
2017-10-09 8:28 ` Michael Kerrisk (man-opages) [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=3f1e2110-e736-0f53-c8a6-12bfcda433f7@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=ablacktshirt@gmail.com \
--cc=linux-man@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