From: "Michael Kerrisk" <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Maxin John <maxin.john-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kosaki.motohiro-+CUm20s59erQFUHtdCDX3A@public.gmane.org
Subject: Re: mlock(2) man page modifications
Date: Thu, 25 Sep 2008 11:16:01 +0200 [thread overview]
Message-ID: <cfd18e0f0809250216o7a12899du5e62a1ca049439cb@mail.gmail.com> (raw)
In-Reply-To: <9debc4410809240747h5e74e3eft39f4231db0d9cf2c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Maxin, Kosaki,
> As per the mlock(2) implementation bugfix which is present in
> Linux 2.6.27-rc2 git commit,
> (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a477097d9c37c1cf289c7f0257dffcfa42d50197),
> the mlock(2) man page should be modified to reflect the latest changes
> in the kernel.
>
> See the LKML thread regarding this commit :
> http://www.nabble.com/mlock()-return-value-issue-in-kernel-2.6.23.17-td18751601.html
>
> This patch modifies the mlock(2) behaviour as per the SUSv3 specification.
>
> [ENOMEM]
> Some or all of the address range specified by the addr and
> len arguments does not correspond to valid mapped pages
> in the address space of the process.
>
> [EAGAIN]
> Some or all of the memory identified by the operation could not
> be locked when the call was made.
Thanks for your patch! (Kosaki, thanks for your additional comments.)
A few pointers for future patches:
* Your subject line was good, but could have been even more
descriptive. I changed the patch title to: mlock.2: Add EAGAIN error.
* It's best to make the patch the very last piece of the message: put
the Signed-off-by and other text above the patch. This makes the mail
easier for me to read, and to process in git.
I've applied your patch for 3.11.
Cheers,
Michael
> Patch for the mlock.2 to include information about EAGAIN.
> ==========================================================
>
> diff -uNr man-pages-3.10/man2/mlock.2 man-pages-3.10_mlock/man2/mlock.2
> --- man-pages-3.10/man2/mlock.2 2008-09-23 19:22:25.000000000 +0530
> +++ man-pages-3.10_mlock/man2/mlock.2 2008-09-24 19:38:27.786315672 +0530
> @@ -175,6 +175,10 @@
> .B ENOMEM
> Some of the specified address range does not correspond to mapped
> pages in the address space of the process.
> +.TP
> +.B EAGAIN
> +Some of the memory identified by the operation could not be locked when
> +the function call was made.
> .LP
> For
> .BR mlockall ():
>
> =================================================================
>
> Signed-off-by: Maxin B. John <maxin.john-qujY0cBTTHtBDgjK7y7TUQ@public.gmane.org>
>
> Kindly let me know if there are any issues with respect to this modification.
>
> Thanks and Regards,
>
> Maxin B. John
> Sony India Software Center
> Bangalore, India
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-09-25 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9debc4410809240747h5e74e3eft39f4231db0d9cf2c@mail.gmail.com>
[not found] ` <9debc4410809240747h5e74e3eft39f4231db0d9cf2c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-24 14:49 ` mlock(2) man page modifications Maxin John
2008-09-25 9:16 ` Michael Kerrisk [this message]
[not found] ` <20080925145503.3552.KOSAKI.MOTOHIRO@jp.fujitsu.com>
[not found] ` <20080925145503.3552.KOSAKI.MOTOHIRO-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-09-25 9:47 ` FW: " Maxin John
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=cfd18e0f0809250216o7a12899du5e62a1ca049439cb@mail.gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=kosaki.motohiro-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maxin.john-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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