From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/5] Linux: Implement a useful version of _startup_fatal
Date: Tue, 03 May 2022 22:16:34 +0200 [thread overview]
Message-ID: <8735hqe5i5.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <7d39fd76-9802-03ca-0a24-bff8223eb53e@linaro.org> (Adhemerval Zanella via Libc-alpha's message of "Tue, 3 May 2022 14:01:42 -0300")
* Adhemerval Zanella via Libc-alpha:
> On 03/05/2022 13:57, Florian Weimer via Libc-alpha wrote:
>> * H. J. Lu:
>>
>>> On Tue, May 3, 2022 at 9:44 AM Florian Weimer <fweimer@redhat.com> wrote:
>>>>
>>>> * H. J. Lu:
>>>>
>>>>> On Tue, May 3, 2022 at 9:01 AM Florian Weimer <fweimer@redhat.com> wrote:
>>>>>>
>>>>>> * H. J. Lu:
>>>>>>
>>>>>>> The startup codes can't use cancellation before it is ready. Do we need to
>>>>>>> check SHARED in this case?
>>>>>>
>>>>>> I think __libc_fatal shouldn't be a cancellation point. That's not
>>>>>> really related to SHARED.
>>>>>
>>>>> Should we define _startup_fatal unconditionally and always define
>>>>> I386_USE_SYSENTER as 0 for i386 so that _startup_fatal can be
>>>>> used safely during startup?
>>>>
>>>> Hmm. Isn't that what my patch does?
>>>>
>>>
>>> Your patch still checks BUILD_PIE_DEFAULT and SHARED.
>>
>> Ah, I see, thanks. You are right, the i386 version should define
>> I386_USE_SYSENTER unconditionally. Will fix.
>
> I think you might want to check ia64 as well, since it uses a TCB variable
> to call the syscall in some cases.
“might want to check“ isn't a phrase I would use in the context with
ia64, but yes, I can add a startup.h file for it, too. Thanks for the
suggestion.
Florian
next prev parent reply other threads:[~2022-05-03 20:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 19:15 [PATCH 0/5] Linux: Fall back to mmap if early sbrk fails Florian Weimer
2022-05-02 19:15 ` [PATCH 1/5] Linux: Implement a useful version of _startup_fatal Florian Weimer
2022-05-02 19:45 ` H.J. Lu
2022-05-02 19:52 ` Florian Weimer
2022-05-02 20:06 ` H.J. Lu
2022-05-02 20:37 ` Florian Weimer
2022-05-03 5:18 ` Florian Weimer
2022-05-03 15:54 ` H.J. Lu
2022-05-03 16:00 ` Florian Weimer
2022-05-03 16:36 ` H.J. Lu
2022-05-03 16:43 ` Florian Weimer
2022-05-03 16:46 ` H.J. Lu
2022-05-03 16:57 ` Florian Weimer
2022-05-03 17:01 ` Adhemerval Zanella
2022-05-03 20:16 ` Florian Weimer [this message]
2022-05-02 19:15 ` [PATCH 2/5] Linux: Define MMAP_CALL_INTERNAL Florian Weimer
2022-05-03 18:30 ` Florian Weimer
2022-05-04 13:10 ` Stefan Liebler
2022-05-02 19:15 ` [PATCH 3/5] i386: Remove OPTIMIZE_FOR_GCC_5 from Linux libc-do-syscall.S Florian Weimer
2022-05-02 19:20 ` H.J. Lu
2022-05-02 19:15 ` [PATCH 4/5] i386: Honor I386_USE_SYSENTER for 6-argument Linux system calls Florian Weimer
2022-05-02 19:24 ` H.J. Lu
2022-05-02 19:15 ` [PATCH 5/5] csu: Implement and use _dl_early_allocate during static startup Florian Weimer
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=8735hqe5i5.fsf@oldenburg.str.redhat.com \
--to=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).