From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Juergen Gross <jgross@suse.com>
Cc: minios-devel@lists.xenproject.org,
xen-devel@lists.xenproject.org,
Jason Andryuk <jason.andryuk@amd.com>
Subject: Re: [MINI-OS PATCH v2 2/2] 9pfs: add lseek file operation hook
Date: Sun, 23 Mar 2025 01:02:51 +0100 [thread overview]
Message-ID: <Z99PqxXpRnYCupoD@begin> (raw)
In-Reply-To: <20250321093145.17882-3-jgross@suse.com>
Juergen Gross, le ven. 21 mars 2025 10:31:45 +0100, a ecrit:
> Add a file operations lseek hook to the 9pfs frontend. Just use the
> lseek_default() implementation.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Jason Andryuk <jason.andryuk@amd.com>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
> 9pfront.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/9pfront.c b/9pfront.c
> index 7257a07e..8bf3a91e 100644
> --- a/9pfront.c
> +++ b/9pfront.c
> @@ -1325,6 +1325,7 @@ static const struct file_ops ops_9pfs = {
> .write = write_9pfs,
> .close = close_9pfs,
> .fstat = fstat_9pfs,
> + .lseek = lseek_default,
> };
>
> __attribute__((constructor))
> --
> 2.43.0
>
prev parent reply other threads:[~2025-03-23 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 9:31 [MINI-OS PATCH v2 0/2] 9pfs: add some file operation hooks Juergen Gross
2025-03-21 9:31 ` [MINI-OS PATCH v2 1/2] 9pfs: add fstat file operation hook Juergen Gross
2025-03-23 0:01 ` Samuel Thibault
2025-03-23 14:57 ` Jürgen Groß
2025-03-23 14:58 ` Samuel Thibault
2025-03-24 10:21 ` Jan Beulich
2025-03-24 10:30 ` Samuel Thibault
2025-03-24 11:18 ` Jürgen Groß
2025-03-24 11:26 ` Jan Beulich
2025-03-21 9:31 ` [MINI-OS PATCH v2 2/2] 9pfs: add lseek " Juergen Gross
2025-03-23 0:02 ` Samuel Thibault [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=Z99PqxXpRnYCupoD@begin \
--to=samuel.thibault@ens-lyon.org \
--cc=jason.andryuk@amd.com \
--cc=jgross@suse.com \
--cc=minios-devel@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.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.