linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] powerpc/32: remove bogus ppc_select syscall
Date: Wed, 10 Mar 2021 11:00:03 +0100	[thread overview]
Message-ID: <CAK8P3a2W9H7k2S3Bk1323Ro2F=_m48wBy-tENd-MyNe3Z3azyQ@mail.gmail.com> (raw)
In-Reply-To: <13737de5-0eb7-e881-9af0-163b0d29a1a0@csgroup.eu>

On Tue, Mar 9, 2021 at 4:59 PM Christophe Leroy
<christophe.leroy@csgroup.eu> wrote:
> Le 05/03/2021 à 13:03, Arnd Bergmann a écrit :
> > On Fri, Mar 5, 2021 at 11:15 AM Christophe Leroy
> > <christophe.leroy@csgroup.eu> wrote:
> >> Le 05/03/2021 à 11:06, Arnd Bergmann a écrit :
>
> I had another look. In fact x86, arm and m68k still have the #82 syscall, but they don't have the
> hack we have on powerpc to "guess" that something is calling the old select with the arguments of
> the new select.

Makes sense. At least for x86, there are probably still some pre-glibc
binaries around
that would use the old select.

> As part of my series of user accesses cleanup, I'll replace the open coded stuff by a call to
> sys_old_select(), see below.

Nice!

> Maybe at the end we should keep the #82 syscall, but do we need to keep the powerpc hack really ?
> Maybe the best is to drop ppc_select() function but mention sys_old_select() instead of ni_syscall
> for entry #82 in the syscall table ?

I'd say we should either keep the powerpc hack intact (with your cleanup),
or remove the syscall entirely. I have been unable to find any indication of
who might have called the #82 syscall prior to mklinux DR2.1 and linuxppc R4,
so there is no way of knowing which of the two ABIs they were using either.

It was definitely ambiguous since the ancient kernels only had sys_select()
semantics at #82, but the existence of the hack tells us that there were at
least some binaries that wanted the sys_oldselect() semantics.

       Arnd

      reply	other threads:[~2021-03-10 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  8:40 [PATCH v3] powerpc/32: remove bogus ppc_select syscall Christophe Leroy
2021-03-05 10:06 ` Arnd Bergmann
2021-03-05 10:15   ` Christophe Leroy
2021-03-05 12:03     ` Arnd Bergmann
2021-03-09 15:59       ` Christophe Leroy
2021-03-10 10:00         ` Arnd Bergmann [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='CAK8P3a2W9H7k2S3Bk1323Ro2F=_m48wBy-tENd-MyNe3Z3azyQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 NNTP newsgroup(s).