From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH 2/4] 9pfs: Don't use file descriptors in core code
Date: Tue, 11 Mar 2025 15:18:45 +0100 [thread overview]
Message-ID: <3577848.jiUZ1Cz8uQ@silver> (raw)
In-Reply-To: <20250311150313.5e3a7e52@bahia>
On Tuesday, March 11, 2025 3:03:13 PM CET Greg Kurz wrote:
> On Tue, 11 Mar 2025 12:13:06 +0100
> Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
>
> > On Monday, March 10, 2025 6:10:59 PM CET Greg Kurz wrote:
[...]
> > Follow-up on previous patch, this could be reduced to:
> >
> > static int local_fid_fd(int fid_type, V9fsFidOpenState *fs)
> > {
> > if (fid_type == P9_FID_DIR && fs->dir.stream != NULL) {
> > return dirfd(fs->dir.stream);
> > } else if (fid_type == P9_FID_FILE) {
> > return fs->fd;
> > }
> > return -1; /* POSIX invalid file handle */
> > }
> >
> > or even:
> >
> > static int local_fid_fd(int fid_type, V9fsFidOpenState *fs)
> > {
> > return (fid_type == P9_FID_DIR && fs->dir.stream != NULL) ?
> > dirfd(fs->dir.stream) :
> > (fid_type == P9_FID_FILE) ? fs->fd :
> > -1; /* POSIX invalid file handle */
> > }
> >
>
> Yuck, I'll stick to the `if` version ;-)
>
> No sure to understand the meaning of `/* POSIX invalid file handle */` though...
"invalid file descriptor" rather than "invalid file handle". What I mean is
that outside of the Unix world -1 is not necessarily the predefined and
reserved value for "invalid file descriptor".
But no big deal.
/Christian
next prev parent reply other threads:[~2025-03-11 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 17:10 [PATCH 0/4] 9pfs: Fix ftruncate-after-unlink Greg Kurz
2025-03-10 17:10 ` [PATCH 1/4] 9pfs: local : Introduce local_fid_fd() helper Greg Kurz
2025-03-11 10:58 ` Christian Schoenebeck
2025-03-11 14:01 ` Greg Kurz
2025-03-10 17:10 ` [PATCH 2/4] 9pfs: Don't use file descriptors in core code Greg Kurz
2025-03-11 11:13 ` Christian Schoenebeck
2025-03-11 14:03 ` Greg Kurz
2025-03-11 14:13 ` Greg Kurz
2025-03-11 14:18 ` Christian Schoenebeck [this message]
2025-03-10 17:11 ` [PATCH 3/4] 9pfs: Introduce ftruncate file op Greg Kurz
2025-03-11 11:19 ` Christian Schoenebeck
2025-03-10 17:11 ` [PATCH 4/4] 9pfs: Introduce futimens " Greg Kurz
2025-03-11 11:25 ` Christian Schoenebeck
2025-03-11 10:51 ` [PATCH 0/4] 9pfs: Fix ftruncate-after-unlink 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=3577848.jiUZ1Cz8uQ@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--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 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).