From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] nptl: Remove __ASSUME_SET_ROBUST_LIST
Date: Wed, 19 Apr 2017 21:02:00 -0000 [thread overview]
Message-ID: <85d36884-2c64-c585-f07b-f302ab8c7aaf@linaro.org> (raw)
In-Reply-To: <cc192069-95aa-c58f-a6b3-063e260a5644@redhat.com>
On 19/04/2017 15:09, Florian Weimer wrote:
> On 04/19/2017 07:38 PM, Adhemerval Zanella wrote:
>> On Wed, Apr 19, 2017 at 12:28 PM, Florian Weimer <fweimer@redhat.com> wrote:
>>> On 04/19/2017 04:17 PM, Adhemerval Zanella wrote:
>>>>
>>>> The problem is kernel supports for some architecture depends of kernel
>>>> config
>>>> and the underlying hardware revision/model.
>>>
>>>
>>> I understand that. But I have seen a lot of use of robust mutexes lately,
>>> and I'm sure these developers aren't aware that the mutexes aren't portable
>>> across GNU/Linux (the Linux architecture subset supported by glibc).
>>>
>>> I expect it's like the missing accept4 system callâyou need to provide the
>>> set_robust_list system call in the kernel if you want to a working, modern
>>> system.
>>
>> But my point is with current minimum supported kernel version for some
>> architectures
>> we can't simple assume set_robust_list support and even bumping minimum kernel
>> version for some architectures also do not solve the issue (on mips
>> for instance).
>
> Hmm, maybe you are right, and we have to keep things this way for now.
>
> But I don't like that your patch reintroduces the conditional code. You could use
>
> #define __set_robust_list_avail 1
>
> for the __ASSUME_SET_ROBUST_LIST case to reduce clutter, and let GCC do the rest.
>
> Thanks,
> Florian
Alright, I will change it and send a new version.
next prev parent reply other threads:[~2017-04-19 21:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 21:13 Adhemerval Zanella
2017-04-18 21:13 ` [PATCH 2/2] linux: Remove __ASSUME_SET_ROBUST_LIST defines Adhemerval Zanella
2017-04-19 5:37 ` [PATCH 1/2] nptl: Remove __ASSUME_SET_ROBUST_LIST Florian Weimer
2017-04-19 14:18 ` Adhemerval Zanella
2017-04-19 14:51 ` Andreas Schwab
2017-04-19 14:52 ` Adhemerval Zanella
2017-04-19 15:28 ` Florian Weimer
2017-04-19 17:38 ` Adhemerval Zanella
2017-04-19 18:09 ` Florian Weimer
2017-04-19 21:02 ` Adhemerval Zanella [this message]
2017-04-20 12:51 ` Adhemerval Zanella
2017-04-20 12:52 ` Florian Weimer
2017-04-20 13:09 ` Adhemerval Zanella
2017-04-20 13:47 ` Florian Weimer
2017-04-20 17:25 ` Adhemerval Zanella
-- strict thread matches above, loose matches on Subject: below --
2016-09-21 14:11 Adhemerval Zanella
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=85d36884-2c64-c585-f07b-f302ab8c7aaf@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).