From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Michal Nazarewicz <mina86@mina86.com>,
libc-alpha@sourceware.org, carlos@systemhalted.org
Subject: Re: [PATCH] linux: sysconf: limit _SC_MAX_ARG to 6 MiB [BZ #25305]
Date: Wed, 7 Apr 2021 15:52:57 -0300 [thread overview]
Message-ID: <5e390f1e-3c31-c4e9-aae0-168f0b4725c7@linaro.org> (raw)
In-Reply-To: <878s5u7x9g.fsf@oldenburg.str.redhat.com>
On 07/04/2021 15:41, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>> It is unfortunate that Linux did not provide a dynamic way to obtain
>> this value, specially since it has changed over versions. So we will
>> need to continue using heuristics.
>
> We can do a binary search using a test binary, perhaps the dynamic
> linker itself. We can probe a few known values first to speed things
> up, I guess.
>
> It's hideous, but given that the kernel doesn't support us here, what
> else can we do?
IMHO being conservative and use the lower bound of all supported kernels.
I really don't think trying to be smart here with dynamic probing
will add much, specially since this upper limit is what kernel will
support from now on.
next prev parent reply other threads:[~2021-04-07 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:10 Michal Nazarewicz
2021-04-07 18:36 ` Adhemerval Zanella
2021-04-07 18:41 ` Florian Weimer
2021-04-07 18:52 ` Adhemerval Zanella [this message]
2021-04-07 19:04 ` Florian Weimer
2021-04-07 19:34 ` Adhemerval Zanella
2021-04-07 19:36 ` Florian Weimer
2021-04-08 1:49 ` Michal Nazarewicz
2021-04-12 20:59 ` Adhemerval Zanella
2021-04-12 21:31 ` Michal Nazarewicz
2021-04-13 11:53 ` Adhemerval Zanella
2021-04-13 12:13 ` Andreas Schwab
2021-04-13 13:36 ` Adhemerval Zanella
2021-04-13 14:41 ` Andreas Schwab
2021-04-13 14:45 ` Adhemerval Zanella
2021-04-13 19:57 ` Michal Nazarewicz
2021-04-13 20:47 ` 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=5e390f1e-3c31-c4e9-aae0-168f0b4725c7@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@systemhalted.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mina86@mina86.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.
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).