All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Eric Blake <eblake@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	G 3 <programmingkidx@gmail.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] git master build failure in 9pfs
Date: Sat, 4 Mar 2017 11:57:35 +0100	[thread overview]
Message-ID: <20170304115735.02a378ee@bahia.lan> (raw)
In-Reply-To: <10a63c3b-26d7-998c-4dcc-c162f144e8b7@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

On Fri, 3 Mar 2017 12:28:01 -0600
Eric Blake <eblake@redhat.com> wrote:

> On 03/03/2017 12:15 PM, Greg Kurz wrote:
> 
> > 
> > O_PATH | O_NOFOLLOW is a special case as described in the last paragraph
> > of O_PATH in the man page:
> > 
> >               If  pathname  is a symbolic link and the O_NOFOLLOW flag is also
> >               specified, then the call returns a file descriptor referring  to
> >               the  symbolic  link.   This  file  descriptor can be used as the
> >               dirfd argument in calls to fchownat(2),  fstatat(2),  linkat(2),
> >               and readlinkat(2) with an empty pathname to have the calls oper‐
> >               ate on the symbolic link.  
> 
> Only when coupled with AT_EMPTY_PATHNAME.  Without that additional flag,
> then it must be a directory.
> 

And we don't use AT_EMPTY_PATHNAME, so this should work indeed.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-03-04 10:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.56273.1488553194.22740.qemu-devel@nongnu.org>
2017-03-03 15:28 ` [Qemu-devel] git master build failure in 9pfs G 3
2017-03-03 15:44   ` Greg Kurz
2017-03-03 15:55     ` G 3
2017-03-03 15:58       ` Peter Maydell
2017-03-03 16:02         ` G 3
2017-03-03 16:14         ` Greg Kurz
2017-03-03 16:21       ` Daniel P. Berrange
2017-03-03 16:38         ` G 3
2017-03-03 16:40         ` Eric Blake
2017-03-03 16:42           ` Daniel P. Berrange
2017-03-03 16:45           ` Eric Blake
2017-03-03 16:43         ` Greg Kurz
2017-03-03 18:11           ` Eric Blake
2017-03-03 18:15             ` Greg Kurz
2017-03-03 18:28               ` Eric Blake
2017-03-04 10:57                 ` Greg Kurz [this message]
     [not found] <mailman.56353.1488479169.22739.qemu-devel@nongnu.org>
2017-03-03  0:30 ` Programmingkid
2017-03-02 17:28 Mark Cave-Ayland
2017-03-02 17:40 ` Daniel P. Berrange
2017-03-02 18:10   ` Peter Maydell
2017-03-03 15:41     ` Greg Kurz
2017-03-03 14:43   ` Mark Cave-Ayland

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=20170304115735.02a378ee@bahia.lan \
    --to=groug@kaod.org \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.