unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stepan Golosunov <stepan@golosunov.pp.ru>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Update kernel-features.h files for Linux 5.1
Date: Fri, 10 May 2019 17:19:38 +0400	[thread overview]
Message-ID: <20190510131938.fonlmcf3mzs6qypr@sghpc.golosunov.pp.ru> (raw)
In-Reply-To: <20190510102713.udgjb6ilygibgd5x@sghpc.golosunov.pp.ru>

10.05.2019 в 14:27:13 +0400 Stepan Golosunov написал(а):
> 09.05.2019 в 23:00:37 +0000 Joseph Myers написал:
> > Linux 5.1 adds missing syscalls to the syscall table for many Linux
> > kernel architectures.  This patch updates the kernel-features.h
> > headers accordingly.  I believe the statfs64 structure used by alpha
> > matches what the new kernel syscalls use, but that should be reviewed
> > carefully.
> > 
> > Tested with build-many-glibcs.py.
> 
> The newly added direct ipc syscalls are different from the old ones:
> 
> 1. They do not accept IPC_64.  This means that __IPC_64 should be set
> to zero when new syscalls are used.  And new syscalls can not be used
> for compat functions like __old_semctl.
> 
> (Hmm.  Is __old_msgctl already buggy due to its use of __IPC_64 when
> __ASSUME_DIRECT_SYSVIPC_SYSCALLS is defined?  Is there any
> architecture with both __ASSUME_DIRECT_SYSVIPC_SYSCALLS and
> __old_msgctl currently?)
> 
> 2. semtimedop does not exist on 32-bit ABIs.  They have
> semtimedop_time64 instead.
> (I also think that ipc with IPCOP_semtimedop was accidentally made to
> behave like semtimedop_time64 in 32-bit builds of linux 5.1.  But that
> would be a kernel bug.)

And, after rereading
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0d6040d4681735dfc47565de288525de405a5c99

3. There is no semop. semtimedop(_time64)? should be used instead.

  reply	other threads:[~2019-05-10 13:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 23:00 Update kernel-features.h files for Linux 5.1 Joseph Myers
2019-05-10 10:27 ` Stepan Golosunov
2019-05-10 13:19   ` Stepan Golosunov [this message]
2019-05-16  7:59     ` Arnd Bergmann
2019-05-16 19:41       ` Stepan Golosunov
2019-05-16 20:56         ` Arnd Bergmann
2019-05-10 15:07   ` Adhemerval Zanella
2019-05-10 15:11     ` Adhemerval Zanella
2019-05-10 16:15       ` Stepan Golosunov
2019-05-10 16:40         ` Adhemerval Zanella
2019-05-16  8:08     ` Arnd Bergmann
2019-05-16 11:15       ` Adhemerval Zanella
2019-05-16 11:34         ` Arnd Bergmann
2019-05-16 12:28           ` Adhemerval Zanella
2019-05-16 12:42             ` Arnd Bergmann
2019-05-13 21:33   ` Joseph Myers
2019-05-16 15:06     ` Adhemerval Zanella

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190510131938.fonlmcf3mzs6qypr@sghpc.golosunov.pp.ru \
    --to=stepan@golosunov.pp.ru \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@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).