From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: RTC_RD_TIME
Date: Wed, 30 Aug 2017 15:55:17 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.1708301511090.21360@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20170830014328.GB19925@brightrain.aerifal.cx>
On Tue, 29 Aug 2017, Rich Felker wrote:
> I don't know any good fix. The problem is that the glibc (and others')
> ioctl function has a signature mismatching the standard one, with an
> unsigned argument instead of signed, and the macro values are outside
> the range of signed int. Fortunately the warning is harmless but
> obviously it can impact builds with -Werror or policy about warnings..
Type confusion causes musl to wrongly pass sign-extended value to the
kernel (instead of zero-extended). That's a real issue, and it's a bit
disappointing you have not mentioned it.
(BSD flavours as well as Linux have 'unsigned long' there, so I don't
understand why it was ok for POSIX to document request type as 'int';
wouldn't it be appropriate for musl to just follow existing practice
here rather than the letter of the standard?)
Without changing the prototype, I think a possible fix is
#ifdef __GNUC__
#define ioctl(fd, req, ...) ioctl(fd, (int)(req), ##__VA_ARGS__)
#endif
(plus a fix in ioctl.c for the sign extension issue)
although I don't understand how the quoted warning appears; I can
produce another one with -Wsign-conversion, but not this.
Alexander
next prev parent reply other threads:[~2017-08-30 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 21:28 RTC_RD_TIME Jorge Almeida
2017-08-30 1:43 ` RTC_RD_TIME Rich Felker
2017-08-30 6:35 ` RTC_RD_TIME Jorge Almeida
2017-08-30 12:55 ` Alexander Monakov [this message]
2017-08-30 15:20 ` RTC_RD_TIME Jorge Almeida
2017-08-30 16:42 ` RTC_RD_TIME Alexander Monakov
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=alpine.LNX.2.20.13.1708301511090.21360@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).