From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>,
Xiaoming Ni <nixiaoming@huawei.com>
Subject: Re: [PATCH 2/3] stdlib: Enforce PATH_MAX on allocated realpath buffer
Date: Tue, 11 Aug 2020 11:54:54 +0200 [thread overview]
Message-ID: <87bljhqzgx.fsf@igel.home> (raw)
In-Reply-To: <877du537w8.fsf@mid.deneb.enyo.de> (Florian Weimer's message of "Tue, 11 Aug 2020 10:26:47 +0200")
On Aug 11 2020, Florian Weimer wrote:
> I don't think Linux has such a restriction. One cannot open such
> files directly, but they can exist.
You can open them with a relative name as long as cwd is nearer than
PATH_MAX (or use openat with such a directory handle).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-08-11 9:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 20:48 [PATCH 1/3] stdlib: Use fixed buffer size for realpath (BZ #26241) Adhemerval Zanella
2020-08-10 20:48 ` [PATCH 2/3] stdlib: Enforce PATH_MAX on allocated realpath buffer Adhemerval Zanella
2020-08-11 8:26 ` Florian Weimer
2020-08-11 9:54 ` Andreas Schwab [this message]
2020-08-11 10:24 ` Florian Weimer
2020-08-11 15:05 ` Adhemerval Zanella
2020-08-11 15:37 ` Paul Eggert
2020-08-11 18:29 ` Florian Weimer
2020-08-11 9:48 ` Andreas Schwab
2020-08-10 20:48 ` [PATCH 3/3] linux: Optimize realpath stack usage Adhemerval Zanella
2020-08-10 21:25 ` Paul Eggert
2020-08-11 14:14 ` Adhemerval Zanella
2020-08-11 15:18 ` Adhemerval Zanella
2020-08-11 15:52 ` Paul Eggert
2020-08-11 19:01 ` Adhemerval Zanella
2020-08-11 16:46 ` Andreas Schwab
2020-08-17 14:00 ` Dmitry V. Levin
2020-08-17 15:13 ` Andreas Schwab
2020-08-17 16:17 ` Dmitry V. Levin
2020-08-11 9:46 ` Andreas Schwab
2020-08-11 0:32 ` [PATCH 1/3] stdlib: Use fixed buffer size for realpath (BZ #26241) Matt Turner
2020-08-11 3:00 ` Xiaoming Ni
2020-08-11 14:57 ` Adhemerval Zanella
2020-08-12 1:38 ` Xiaoming Ni
2020-08-12 23:04 ` Adhemerval Zanella
2020-08-13 20:29 ` 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=87bljhqzgx.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=nixiaoming@huawei.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).