From: Max Reitz <mreitz@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, Miklos Szeredi <mszeredi@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
virtio-fs@redhat.com, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Vivek Goyal" <vgoyal@redhat.com>
Subject: Re: virtiofsd: sshfs as submount?
Date: Mon, 21 Dec 2020 13:49:07 +0100 [thread overview]
Message-ID: <06de2310-e566-61a7-9ae8-679e9fefabc3@redhat.com> (raw)
In-Reply-To: <c0f7c512-d796-db16-e5fb-a2e346c37e48@redhat.com>
On 21.12.20 13:45, Laszlo Ersek wrote:
> On 12/21/20 13:06, Max Reitz wrote:
>
>> I can share sshfs through sshfs, so it must be something virtiofs-specific.
>
> Your insight proved crucial to solving the riddle.
>
> Chaining sshfs with sshfs made me think that you must have used a normal
> (non-root) user account on the first remote computer (where you ran the
> 2nd sshfs command).
>
> And that reminded me of the "allow_root" option which I seemed to have
> read somewhere around the FUSE manuals.
Oh, that makes sense. Right.
> So indeed I set up another sshfs mount on my laptop, with my normal UID,
> and tried to access the mount point from a plain root shell (with
> virtiofsd completely out of the picture) -- it failed with "Permission
> denied". :) It's apparently intentional on sshfs's / FUSE's part, to
> protect the local root user from "remote nastiness injection".
>
> Then I re-did the sshfs mount, but with "-o allow_root" this time. The
> plain root shell can now access the mount point.
Indeed, that works better.
> ... So can virtiofsd :) It's *amazing* to see remote files in the UEFI
> shell. I never thought "filesystem as a service" could feel this empowering.
>
> Thanks, Max!
Er, *cough*, my pleasure! O:)
Max
prev parent reply other threads:[~2020-12-21 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 23:41 virtiofsd: sshfs as submount? Laszlo Ersek
2020-12-21 12:06 ` Max Reitz
2020-12-21 12:23 ` Laszlo Ersek
2020-12-21 12:45 ` Laszlo Ersek
2020-12-21 12:49 ` Max Reitz [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=06de2310-e566-61a7-9ae8-679e9fefabc3@redhat.com \
--to=mreitz@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lersek@redhat.com \
--cc=mszeredi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.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 NNTP newsgroup(s).