From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] lib/cloner.c: Use __clone instead of clone for s390
Date: Fri, 8 May 2020 10:20:14 -0400 (EDT) [thread overview]
Message-ID: <475724112.11805789.1588947614752.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <8f28b9797be3408c0c1086d0a2bc9c052b55bfe2.1588942426.git.agordeev@linux.ibm.com>
----- Original Message -----
> The kernel sys_clone and s390 glibc entry __clone assume
> the flags parameter type as unsigned long. However, the
> glibc clone wrapper used by ltp_clone helper defines flags
> as signed int. That leads to gcc extending CLONE_IO flag of
> 0x80000000 value to 0xffffffff80000000.
Same problem exists on ppc64le. There's a patch proposed to fix this on
kernel side:
https://lore.kernel.org/lkml/20200507103214.77218-1-christian.brauner@ubuntu.com/
Earlier discussion is here:
https://sourceware.org/pipermail/libc-alpha/2020-May/113596.html
next prev parent reply other threads:[~2020-05-08 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 13:09 [LTP] [PATCH 0/2] syscalls/kcmp03.c: Fix CLONE_IO failure on s390 Alexander Gordeev
2020-05-08 13:09 ` [LTP] [PATCH 1/2] syscalls/kcmp03.c: Extend clone_type type to unsigned long Alexander Gordeev
2020-05-08 13:09 ` [LTP] [PATCH 2/2] lib/cloner.c: Use __clone instead of clone for s390 Alexander Gordeev
2020-05-08 14:20 ` Jan Stancek [this message]
2020-05-11 8:33 ` Petr Vorel
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=475724112.11805789.1588947614752.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.