From: Richard Weinberger <richard@nod.at>
To: Guillem Jover <guillem@hadrons.org>
Cc: Jesper Juhl <jj@chaosbits.net>, Al Viro <viro@ZenIV.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: st_size of a symlink
Date: Tue, 24 Jul 2012 12:16:59 +0200 [thread overview]
Message-ID: <500E761B.4040705@nod.at> (raw)
In-Reply-To: <20120723231333.GA1299@gaara.hadrons.org>
On 24.07.2012 01:13, Guillem Jover wrote:
> Well, can't the link be accessed when getting the stat information
> then?
Sure, but it's not trivial.
>> IMHO the lstat() and readlink() manpages have to be more precise
>> about st_size.
>
> They document what POSIX says:
This does not make it any better...
Thanks,
//richard
prev parent reply other threads:[~2012-07-24 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:55 st_size of a symlink Richard Weinberger
2012-07-23 18:09 ` Jesper Juhl
2012-07-23 20:22 ` Al Viro
2012-07-23 20:47 ` Jesper Juhl
2012-07-23 22:07 ` Richard Weinberger
2012-07-23 23:13 ` Guillem Jover
2012-07-24 10:16 ` Richard Weinberger [this message]
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=500E761B.4040705@nod.at \
--to=richard@nod.at \
--cc=guillem@hadrons.org \
--cc=jj@chaosbits.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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