From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: <libc-help@sourceware.org>
Subject: question about prctl return value type
Date: Wed, 24 Jul 2019 10:01:00 -0000 [thread overview]
Message-ID: <5D382C5F.6020806@cn.fujitsu.com> (raw)
Hi All
Since kernel syscall use long value for return, why we set int in sys/prctl.h(glibc). as below:
/include/sys/prctl.h
1 #ifndef _SYS_PRCTL_H
2 #include_next <sys/prctl.h>
3
4 # ifndef _ISOMAC
5
6 extern int __prctl (int __option, ...);
7
8 # endif /* !_ISOMAC */
9 #endif
If we calling prctl(PR_SET_TIMERSLACK, ULONG_MAX) and then calling prctl(PR_GET_TIMERSLACK), the value
will be truncated into INT_MAX(or convered into unsinged,it is UINT_MAX) on 64bit machine. Or, this is a
glibc limitation for prctl interfaces?
ps:After kernel commit da8b44d5a9f ("timer: convert timer_slack_ns from unsigned long to u64"),
we limit under ULONG_MAX when calling PR_GET_TIMERSLACK. I think we can use long instead of int in sys/prctl.h.
Thanks
Yang Xu
next reply other threads:[~2019-07-24 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 10:01 Yang Xu [this message]
2019-07-24 10:48 ` Florian Weimer
2019-07-25 7:53 ` Yang Xu
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=5D382C5F.6020806@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).