From: stefanx <stefanx@lrz.uni-muenchen.de>
To: QEMU / QEMU
<incoming+a5b7554ee57f194421d0557ae5d491ed@incoming.gitlab.com>,
virtio-fs@redhat.com
Subject: Re: [Virtio-fs] QEMU | virtiofsd: doesn't garant write access at users allowed by group permission (#368)
Date: Tue, 4 Apr 2023 22:06:42 +0200 [thread overview]
Message-ID: <a0874daf-a63a-eb2a-76e8-a57f63ab9f6e@lrz.uni-muenchen.de> (raw)
In-Reply-To: <note_1341159092@gitlab.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Am 04.04.23 um 19:51 schrieb GK (@hgkamath):
> GitLab
>
> GK <https://gitlab.com/hgkamath> commented <https://gitlab.com/qemu-project/qemu/-/issues/368#note_1341159092>:
>
> Just a user here.
>
> There is some fuse update going into Linux kernel 6.3
>
> * 20230227 Miklos Szeredi [GIT PULL] fuse update for 6.3 https://lore.kernel.org/lkml/Y%2FzYyN7NeLKusmSj@miu.piliscsaba.redhat.com/
>
> Unsure if it will address the issue.
> In any case, virtiofsd and qemu, may need to some code updates to make use of the new feature.
>
> —
> Reply to this email directly or view it on GitLab <https://gitlab.com/qemu-project/qemu/-/issues/368#note_1341159092>.
> You're receiving this email because of your account on gitlab.com <https://gitlab.com>. Unsubscribe <https://gitlab.com/-/sent_notifications/a5b7554ee57f194421d0557ae5d491ed/unsubscribe> from this thread · Manage all notifications <https://gitlab.com/-/profile/notifications> · Help <https://gitlab.com/help>
>
Thank you, I hope there is soon an update for Ubuntu.
[-- Attachment #2: Type: text/html, Size: 4117 bytes --]
parent reply other threads:[~2023-04-04 20:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <note_1341159092@gitlab.com>]
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=a0874daf-a63a-eb2a-76e8-a57f63ab9f6e@lrz.uni-muenchen.de \
--to=stefanx@lrz.uni-muenchen.de \
--cc=incoming+a5b7554ee57f194421d0557ae5d491ed@incoming.gitlab.com \
--cc=virtio-fs@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).