public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: Restartable Sequences system call merged into Linux
Date: Wed, 11 Jul 2018 17:59:00 -0000	[thread overview]
Message-ID: <cf83696f-56f4-eed3-1691-faddd38a9520@linaro.org> (raw)
In-Reply-To: <de322e75-b4fd-ae9f-d864-2d951026dd5a@redhat.com>



On 11/07/2018 14:45, Florian Weimer wrote:
> On 07/11/2018 07:42 PM, Adhemerval Zanella wrote:
>> I did not dig into to check what it would require to fix this issue,
>> however only x86, sparc, and s390 seems to be affected.
> 
> It should affect all architectures, with varying symptoms, due to the way we allocate the TCB off thread stacks.

It seems for TLS_DTV_AT_TP the static tls alignment is indeed
take in consideration (at least the bug report testcase does
not fail on aarch64 or powerpc64le). I need to remind better
how all these fields are layout on different ABIs...

> 
>> But thinking
>> twice, it seems we can live with this issue at least for 2.28.
> 
> And we should be able to backport the fix if it happens early enough during 2.29 development.
> 
> Thanks,
> Florian

  reply	other threads:[~2018-07-11 17:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 19:49 Mathieu Desnoyers
2018-06-11 19:55 ` Florian Weimer
2018-06-11 20:04   ` Mathieu Desnoyers
2018-06-12 13:11     ` Florian Weimer
2018-06-12 16:31       ` Mathieu Desnoyers
2018-06-13  8:23         ` Florian Weimer
2018-06-14 12:28         ` Pavel Machek
2018-06-14 13:02           ` Mathieu Desnoyers
2018-06-14 13:26             ` Pavel Machek
2018-06-14 13:32               ` Florian Weimer
2018-06-14 13:46                 ` Mathieu Desnoyers
2018-06-15  5:10                   ` Florian Weimer
2018-06-15 17:44                     ` Mathieu Desnoyers
2018-06-14 13:38               ` Mathieu Desnoyers
2018-06-14 13:50                 ` Pavel Machek
2018-06-14 14:01                   ` Florian Weimer
2018-06-14 14:36                     ` Mathieu Desnoyers
2018-06-14 14:41                       ` Florian Weimer
2018-06-14 15:09                         ` Mathieu Desnoyers
2018-06-15  5:09             ` Florian Weimer
2018-06-15 17:50               ` Mathieu Desnoyers
2018-06-15  5:07           ` Florian Weimer
2018-06-13 11:48 ` Heiko Carstens
2018-06-13 16:14   ` Mathieu Desnoyers
2018-06-13 19:53     ` Mathieu Desnoyers
2018-07-11 16:03 ` Stefan Liebler
2018-07-11 16:23   ` Adhemerval Zanella
2018-07-11 17:19     ` Florian Weimer
2018-07-11 17:42       ` Adhemerval Zanella
2018-07-11 17:45         ` Florian Weimer
2018-07-11 17:59           ` Adhemerval Zanella [this message]
2018-07-12  8:08           ` Stefan Liebler
2018-07-11 19:05       ` Carlos O'Donell
2018-07-12  8:10   ` Szabolcs Nagy
2018-07-13 13:22     ` Stefan Liebler

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=cf83696f-56f4-eed3-1691-faddd38a9520@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.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).