From: tecufanujacu@tutanota.com
To: virtio-fs@redhat.com
Subject: [Virtio-fs] virtiofsd: doesn't garant write access at users allowed by group permission
Date: Tue, 1 Jun 2021 17:55:11 +0200 (CEST) [thread overview]
Message-ID: <Mb7HI6c--3-2@tutanota.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hello to everyone,
I'm trying virtiofsd with proxmox from few weeks and I noticed a problem, virtiofsd doesn't garant write access at users allowed by group permission.
The virtiofsd bin included in proxmox is v 7.32, but I have also tested the bins compiled from source from stable branch (v7.27) and dev branch (v7.33), and I also have tested the bin virtiofsd-rs. Always same problem.
I opened an issue on gitlab and I asked in the proxmox forum but with almost zero interaction. Seems to me that virtiofsd isn't a lot used. Someone suggested me to write in the mailinglist for these technical things and here I am.
To better make understand what problem I'm noticing I link the issue opened in the gitlab in which I have reported a lot of useful info and logs with a good formatting:
https://gitlab.com/qemu-project/qemu/-/issues/368
To me seems really strange what is happening, am I doing some error or this really is a virtiofsd bug?
[-- Attachment #2: Type: text/html, Size: 4404 bytes --]
next reply other threads:[~2021-06-01 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 15:55 tecufanujacu [this message]
2021-06-02 8:32 ` [Virtio-fs] virtiofsd: doesn't garant write access at users allowed by group permission Chirantan Ekbote
2021-06-02 13:17 ` Dr. David Alan Gilbert
2021-06-04 13:16 ` Vivek Goyal
2021-06-04 18:30 ` tecufanujacu
2021-06-07 15:51 ` Harry G. Coin
-- strict thread matches above, loose matches on Subject: below --
2021-06-18 23:28 Ameer Ghani
2021-06-22 13:45 ` Vivek Goyal
2021-06-24 14:23 ` Ameer Ghani
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=Mb7HI6c--3-2@tutanota.com \
--to=tecufanujacu@tutanota.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 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.