From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org, Akihiko Odaki <akihiko.odaki@gmail.com>
Subject: Re: [PATCH] 9pfs: local: Do not follow symlink in _nofollow
Date: Wed, 27 Apr 2022 12:21:51 +0200 [thread overview]
Message-ID: <20220427122151.6a22267b@bahia> (raw)
In-Reply-To: <3805748.cZurrHcIA4@silver>
On Wed, 27 Apr 2022 10:46:31 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> On Mittwoch, 27. April 2022 04:45:45 CEST Akihiko Odaki wrote:
> > Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
> > ---
> > hw/9pfs/9p-local.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/hw/9pfs/9p-local.c b/hw/9pfs/9p-local.c
> > index d42ce6d8b82..def8afdb4d6 100644
> > --- a/hw/9pfs/9p-local.c
> > +++ b/hw/9pfs/9p-local.c
> > @@ -365,7 +365,7 @@ static int fchmodat_nofollow(int dirfd, const char
> > *name, mode_t mode) if (fd == -1) {
> > /* In case the file is writable-only and isn't a directory. */
> > if (errno == EACCES) {
> > - fd = openat_file(dirfd, name, O_WRONLY, 0);
> > + fd = openat_file(dirfd, name, O_WRONLY | O_NOFOLLOW, 0);
>
> O_NOFOLLOW flag is always added inside openat_file() implementation:
>
> https://github.com/qemu/qemu/blob/master/hw/9pfs/9p-util.h#L60
>
> So this change is not necessary AFAICS.
>
Right, and with macOS in mind, maybe fchmodat(AT_SYMLINK_NOFOLLOW) just
works unlike with linux ?
> > }
> > if (fd == -1 && errno == EISDIR) {
> > errno = EACCES;
>
>
next prev parent reply other threads:[~2022-04-27 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 2:45 [PATCH] 9pfs: local: Do not follow symlink in _nofollow Akihiko Odaki
2022-04-27 8:46 ` Christian Schoenebeck
2022-04-27 10:21 ` Greg Kurz [this message]
2022-04-27 11:18 ` Christian Schoenebeck
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=20220427122151.6a22267b@bahia \
--to=groug@kaod.org \
--cc=akihiko.odaki@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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 NNTP newsgroup(s).