From: Rich Felker <dalias@libc.org>
To: Andrey Bugaevskiy <bugaevskiy@yandex-team.ru>
Cc: 'Florian Weimer' <fweimer@redhat.com>, musl@lists.openwall.com
Subject: Re: [musl] errno and swapcontext in a multithreaded setup
Date: Thu, 8 Apr 2021 14:55:11 -0400 [thread overview]
Message-ID: <20210408185511.GC2546@brightrain.aerifal.cx> (raw)
In-Reply-To: <001e01d72c9f$09d1b700$1d752500$@yandex-team.ru>
On Thu, Apr 08, 2021 at 08:46:00PM +0300, Andrey Bugaevskiy wrote:
> On Thu, 8 Apr 2021, Florian Weimer wrote:
> > * Andrey Bugaevskiy:
> >
> > > I'm using makecontext/swapcontext to migrate contexts between threads
> > > and this sometimes leads to getting incorrect errno values.
> > >
> > > Investigating further I've noticed that __errno_location
> > > is marked __attribute__((const)).
> > > This causes optimizers to assume that errno address never changes
> > > in the scope of the function which is not the case in my scenario.
> >
> > The optimizers make the same assumption for actual thread-local
> > variables, not just __errno_location. Migrating contexts between
> > threads results in undefined behavior.
>
> Can you please point me to some explanation why this optimization
> is valid for thread-local variables?
>
> As far as I can imagine optimizer should at least prove that it
> won't be changed from some other place or (if the variable is local
> to the function) that it is not changed by a recursive call.
Perhaps you're confusing the value of errno with its address. No
function can change the address of errno, only its value.
Conceptually, __errno_location() is just &errno.
Rich
next prev parent reply other threads:[~2021-04-08 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 16:10 Andrey Bugaevskiy
2021-04-08 17:04 ` Florian Weimer
2021-04-08 17:17 ` Rich Felker
2021-04-08 17:46 ` Andrey Bugaevskiy
2021-04-08 18:55 ` Rich Felker [this message]
2021-04-09 12:11 ` Andrey Bugaevskiy
2021-04-09 12:15 ` 'Rich Felker'
2021-04-08 17:40 ` Ariadne Conill
2021-04-08 17:49 ` Rich Felker
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=20210408185511.GC2546@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=bugaevskiy@yandex-team.ru \
--cc=fweimer@redhat.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).