From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 75431] posix_fadvise(2): wrong param name?
Date: Sat, 03 May 2014 19:18:42 +0000 [thread overview]
Message-ID: <bug-75431-11311-wvXWRJLBBg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75431-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75431
Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Resolution|--- |CODE_FIX
--- Comment #1 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Eric Siegerman from comment #0)
> In posix_fadvise(2), under "Architecture-specific variants", it says:
> [Due to register-alignment issues,]
> ... the call signature of posix_fadvise() shown in
> the SYNOPSIS would force a register to be wasted as padding between
> the fd and len arguments.
>
> Should it say "offset" instead of "len" in the last line of that quoted bit?
>
> Rationale: the SYNOPSIS shows a call signature of:
> int posix_fadvise(int fd, off_t offset, off_t len, int advice);
> in which:
> - fd and len aren't adjacent
> - it's between a shorter value followed by a longer one that I'd expect
> alignment padding to be needed, and the only pair where that occurs is (fd,
> offset)
The change sounds right to me. I've made it.
> CAVEAT: I'm not familiar with either the syscall or the specific alignment
> issues in question, so my guess about this is just that -- a deduced guess,
> NOT specific knowledge. So don't make the change on my say-so; please
> verify it first!
I'm going to trust you on this one ;-). I was the one who injected the error in
the first place.
--
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:[~2014-05-03 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 19:04 [Bug 75431] New: posix_fadvise(2): wrong param name? bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-75431-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-05-03 19:18 ` 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-75431-11311-wvXWRJLBBg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.