From: "Mark Hatle" <mark.hatle@kernel.crashing.org>
To: Seebs <seebs@seebs.net>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] pseudo: Fix statx function usage
Date: Mon, 12 Oct 2020 14:14:36 -0500 [thread overview]
Message-ID: <a2369d3c-ed7e-b03b-8538-aefe09008288@kernel.crashing.org> (raw)
In-Reply-To: <20201012140849.69cf09fc@seebsdell>
On 10/12/20 2:08 PM, Seebs wrote:
> On Wed, 7 Oct 2020 17:20:18 +0100
> "Richard Purdie" <richard.purdie@linuxfoundation.org> wrote:
>
>> +There is magic in the posts where specific variable names have
>> specific +magic. For that magic to work, "path" needs to be used not
>> "pathname" as +is currently there. Fix this, which fixes path issues
>> on systems using +statx (Ubuntu 20.04 in particular).
>
> So, usually if "pathname" is used, it's intentional to suppress the
> special magic behavior. Usually, but not always. In this case, the man
> page does use "pathname" and sometimes that means it's just a cut and
> paste error.
>
> My man page also says there's no glibc wrapper for statx, making me
> slightly surprised that a wrapper for it is needed/relevant.
I looked into this. It appears (after pseudo was written, but) about 7 or so
years ago, all of the man pages were re-written and the language was changed.
So 'pathname' no longer has the same syntactic meaning that it did when pseudo
was first written. (It's not just statx, I looked at things like fopen, open, etc.)
--Mark
> -s
>
>
>
>
>
next prev parent reply other threads:[~2020-10-12 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 16:20 [PATCH 1/2] pseudo: do not expand symlinks in /proc Richard Purdie
2020-10-07 16:20 ` [PATCH 2/2] pseudo: Fix statx function usage Richard Purdie
2020-10-12 19:08 ` [OE-core] " Seebs
2020-10-12 19:14 ` Mark Hatle [this message]
2020-10-12 19:21 ` Seebs
2020-10-12 20:25 ` Richard Purdie
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=a2369d3c-ed7e-b03b-8538-aefe09008288@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=seebs@seebs.net \
/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