From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Cc: Olaf Meeuwissen <paddy-hack@member.fsf.org>
Subject: Re: [musl] [BUG] ioctl: overflow in implicit constant conversion
Date: Mon, 20 Jan 2020 16:08:35 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.2001201607460.7204@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20200120120930.GO23985@port70.net>
On Mon, 20 Jan 2020, Szabolcs Nagy wrote:
> changing the type is an api and abi break in musl.
> we could try to silence the warning instead (e.g via
> explicit cast in _IOC or in an ioctl macro).
Doesn't the next release with time64 changes give a nice
opportunity to make this change as well?
Alexander
next prev parent reply other threads:[~2020-01-20 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 10:39 Olaf Meeuwissen
2020-01-20 12:09 ` Szabolcs Nagy
2020-01-20 12:57 ` Alexander Monakov
2020-01-20 17:14 ` Rich Felker
2020-01-20 13:08 ` Alexander Monakov [this message]
2020-01-21 12:27 ` Olaf Meeuwissen
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.2001201607460.7204@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=musl@lists.openwall.com \
--cc=paddy-hack@member.fsf.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.
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).