From: Andreas Schwab <schwab@linux-m68k.org>
To: ltp@lists.linux.it
Subject: [LTP] [bug?] clone(CLONE_IO) failing after kernel commit commit ef2c41cf38a7
Date: Tue, 05 May 2020 09:54:38 +0200 [thread overview]
Message-ID: <874ksuke9t.fsf@igel.home> (raw)
In-Reply-To: <1038674044.11248021.1588663714272.JavaMail.zimbra@redhat.com> (Jan Stancek via Libc-alpha's message of "Tue, 5 May 2020 03:28:34 -0400 (EDT)")
On Mai 05 2020, Jan Stancek via Libc-alpha wrote:
> I'm seeing an issue with CLONE_IO and libc' clone() on ppc64le,
> where flags parameter appears to be sign extended before it's passed
> to kernel syscall.
Looks like the flags argument should be declared as unsigned int,
instead of int, both in glibc and in the kernel.
#define CLONE_IO 0x80000000 /* Clone io context */
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2020-05-05 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <100149681.11244932.1588661282331.JavaMail.zimbra@redhat.com>
2020-05-05 7:28 ` [LTP] [bug?] clone(CLONE_IO) failing after kernel commit commit ef2c41cf38a7 Jan Stancek
2020-05-05 7:49 ` Florian Weimer
2020-05-05 7:59 ` Christian Brauner
2020-05-05 8:02 ` Christian Brauner
2020-05-05 8:32 ` Christian Brauner
2020-05-05 8:58 ` Jan Stancek
2020-05-05 9:05 ` Florian Weimer
2020-05-05 9:15 ` Christian Brauner
2020-05-05 9:36 ` Florian Weimer
2020-05-05 9:58 ` Christian Brauner
2020-05-05 10:21 ` Christian Brauner
2020-05-05 11:34 ` Florian Weimer
2020-05-05 11:35 ` Dmitry V. Levin
2020-05-05 11:43 ` Christian Brauner
2020-05-05 11:49 ` Dmitry V. Levin
2020-05-05 11:57 ` Christian Brauner
2020-05-05 11:08 ` Florian Weimer
2020-05-05 11:26 ` Christian Brauner
2020-05-05 7:54 ` Andreas Schwab [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=874ksuke9t.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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.