From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 97051] get_mempolicy(2) inconsistent with numaif.h
Date: Tue, 05 May 2015 09:19:10 +0000 [thread overview]
Message-ID: <bug-97051-11311-tf7awIdcVv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-97051-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=97051
--- Comment #1 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Andi, could you comment on this bug?
Thanks,
Michael
On 22 April 2015 at 00:28, <bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=97051
>
> Bug ID: 97051
> Summary: get_mempolicy(2) inconsistent with numaif.h
> Product: Documentation
> Version: unspecified
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P1
> Component: man-pages
> Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
> Reporter: nyh-TS7m/3hpY0sOpacJJkBjfT4kX+cae0hd@public.gmane.org
> Regression: No
>
> get_mempolicy(2)'s synopsis is:
>
> #include <numaif.h>
>
> int get_mempolicy(int *mode, unsigned long *nodemask,
> unsigned long maxnode, unsigned long addr,
> unsigned long flags);
>
> However, the actual prototype in numif.h (and implementation in numactl's
> syscall.c) is subtly different:
>
> long get_mempolicy(int *policy, const unsigned long *nmask,
> unsigned long maxnode, void *addr, int flags);
>
> The funny thing is, that prototype is isn't quite right either - it pretends
> nmask is a const pointer, but it most definitely isn't, and the data pointed by
> it get written to. But that isn't a man-page bug.
>
> --
> You are receiving this mail because:
> You are watching the assignee of the bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
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
prev parent reply other threads:[~2015-05-05 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 22:28 [Bug 97051] New: get_mempolicy(2) inconsistent with numaif.h bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-97051-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2015-05-05 9:19 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [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=bug-97051-11311-tf7awIdcVv@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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