public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/8] misc: Add time64 alias for ioctl
Date: Tue, 20 Jul 2021 10:52:57 +0200	[thread overview]
Message-ID: <87eebttlhy.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210720103245.491b5bfa@ktm> (Lukasz Majewski's message of "Tue,  20 Jul 2021 10:32:45 +0200")

* Lukasz Majewski:

> So the idea here is to have the distinction for ioctl's when we decide
> to support 64 bit time on 32 bit ports? And as ioctls are often
> multiplexed, we will not be able to distinct the time related struct
> members passed to this syscall?

The idea is this: If we need to add more ioctl rewriting in userspace,
then we can confie that to time64 binaries with this change because they
use a separate function call.  Binaries which use the non-time64
interface (especially old binaries which cannot be recompiled) are
totally unaffected by such potential future changes.

If there is no separate time64 symbols, we would have to hope that we
can identify the need to rewrite based on the arguments alone, which is
likely but not guaranteed.

Thanks,
Florian


  reply	other threads:[~2021-07-20  8:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 13:41 [PATCH 0/8] Additional time64 aliases Florian Weimer
2021-07-05 13:41 ` [PATCH 1/8] misc: Add time64 alias for ioctl Florian Weimer
2021-07-20  8:32   ` Lukasz Majewski
2021-07-20  8:52     ` Florian Weimer [this message]
2021-07-20  9:18       ` Lukasz Majewski
2021-07-20 19:47   ` Adhemerval Zanella
2021-07-05 13:41 ` [PATCH 2/8] io: Add time64 alias for fcntl Florian Weimer
2021-07-20  8:41   ` Lukasz Majewski
2021-07-20  8:45     ` Lukasz Majewski
2021-07-20  8:50     ` Florian Weimer
2021-07-20  9:16       ` Lukasz Majewski
2021-07-20 19:49   ` Adhemerval Zanella
2021-07-05 13:42 ` [PATCH 3/8] Linux: Add time64 alias for prctl Florian Weimer
2021-07-20  8:51   ` Lukasz Majewski
2021-07-20 19:52   ` Adhemerval Zanella
2021-07-05 13:42 ` [PATCH 4/8] socket: Add time64 alias for sendmmsg Florian Weimer
2021-07-20  8:56   ` Lukasz Majewski
2021-07-20 19:55   ` Adhemerval Zanella
2021-07-05 13:42 ` [PATCH 5/8] socket: Add time64 alias for recvmsg Florian Weimer
2021-07-20  8:58   ` Lukasz Majewski
2021-07-20 19:56   ` Adhemerval Zanella
2021-07-05 13:42 ` [PATCH 6/8] socket: Add time64 alias for sendmsg Florian Weimer
2021-07-20  9:02   ` Lukasz Majewski
2021-07-20 20:11   ` Adhemerval Zanella
2021-07-05 13:42 ` [PATCH 7/8] socket: Add time64 alias for getsockopt Florian Weimer
2021-07-20  9:10   ` Lukasz Majewski
2021-07-20  9:17     ` Florian Weimer
2021-07-20 10:25       ` Lukasz Majewski
2021-07-21 20:09   ` Adhemerval Zanella
2021-07-21 20:12     ` Florian Weimer
2021-07-21 20:17       ` Adhemerval Zanella
2021-07-05 13:42 ` [PATCH 8/8] socket: Add time64 alias for setsockopt Florian Weimer
2021-07-20  9:15   ` Lukasz Majewski
2021-07-20  9:18     ` Florian Weimer
2021-07-21 20:10   ` Adhemerval Zanella
2021-07-19 15:28 [PATCH v2 0/8] Additional time64 system call wrappers Florian Weimer
2021-07-19 15:28 ` [PATCH 1/8] misc: Add time64 alias for ioctl Florian Weimer

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=87eebttlhy.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    /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).