From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/4] 9pfs: local : Introduce local_fid_fd() helper
Date: Tue, 11 Mar 2025 15:01:30 +0100 [thread overview]
Message-ID: <20250311150130.7a875e63@bahia> (raw)
In-Reply-To: <23860256.nhtPhaig3F@silver>
On Tue, 11 Mar 2025 11:58:28 +0100
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> On Monday, March 10, 2025 6:10:58 PM CET Greg Kurz wrote:
> > Factor out duplicated code to a single helper. More users to come.
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > hw/9pfs/9p-local.c | 21 +++++++++++----------
> > 1 file changed, 11 insertions(+), 10 deletions(-)
> >
> > diff --git a/hw/9pfs/9p-local.c b/hw/9pfs/9p-local.c
> > index 928523afcc6c..c4366c867988 100644
> > --- a/hw/9pfs/9p-local.c
> > +++ b/hw/9pfs/9p-local.c
> > @@ -766,10 +766,9 @@ out:
> > return err;
> > }
> >
> > -static int local_fstat(FsContext *fs_ctx, int fid_type,
> > - V9fsFidOpenState *fs, struct stat *stbuf)
> > +static int local_fid_fd(int fid_type, V9fsFidOpenState *fs)
> > {
> > - int err, fd;
> > + int fd;
> >
> > if (fid_type == P9_FID_DIR) {
> > fd = dirfd(fs->dir.stream);
> > @@ -777,6 +776,14 @@ static int local_fstat(FsContext *fs_ctx, int fid_type,
> > fd = fs->fd;
> > }
> >
> > + return fd;
> > +}
>
> Maybe simplifying this like:
>
> static int local_fid_fd(int fid_type, V9fsFidOpenState *fs)
> {
> if (fid_type == P9_FID_DIR) {
> return dirfd(fs->dir.stream);
> } else {
> return fs->fd;
> }
> }
>
> or even just:
>
> static int local_fid_fd(int fid_type, V9fsFidOpenState *fs)
> {
> return (fid_type == P9_FID_DIR) ? dirfd(fs->dir.stream) : return fs->fd;
> }
>
I'll go for you suggestion with the `if`. It is clearer than the ternary
expression and it is easier to put a breakpoint. I'm pretty sure all three
result in the same assembly code anyway.
> /Christian
>
> > +
> > +static int local_fstat(FsContext *fs_ctx, int fid_type,
> > + V9fsFidOpenState *fs, struct stat *stbuf)
> > +{
> > + int err, fd = local_fid_fd(fid_type, fs);
> > +
> > err = fstat(fd, stbuf);
> > if (err) {
> > return err;
> > @@ -1167,13 +1174,7 @@ out:
> > static int local_fsync(FsContext *ctx, int fid_type,
> > V9fsFidOpenState *fs, int datasync)
> > {
> > - int fd;
> > -
> > - if (fid_type == P9_FID_DIR) {
> > - fd = dirfd(fs->dir.stream);
> > - } else {
> > - fd = fs->fd;
> > - }
> > + int fd = local_fid_fd(fid_type, fs);
> >
> > if (datasync) {
> > return qemu_fdatasync(fd);
> >
>
>
--
Greg
next prev parent reply other threads:[~2025-03-11 14:02 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 [this message]
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
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=20250311150130.7a875e63@bahia \
--to=groug@kaod.org \
--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).