From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: piaojun <piaojun@huawei.com>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] mount failed in virtio_fs dev 5.1
Date: Tue, 23 Jul 2019 09:31:50 +0100 [thread overview]
Message-ID: <20190723083150.GC2719@work-vm> (raw)
In-Reply-To: <5D36C4EB.4010805@huawei.com>
* piaojun (piaojun@huawei.com) wrote:
> Hi,
>
> I got a problem when mounting virtiofs in kernel5.1 as below:
>
> fuse: loading out-of-tree module taints kernel.
> fuse: module verification failed: signature and/or required key missing - tainting kernel
> fuse init (API version 7.29)
> virtio_fs virtio1: Cache len: 0x80000000 @ 0x180000000
> virtio1 initialised, 524288 pages in 12ms
> virtio_fs_find_instance: fs->tag myfs, tag /dev/null
> virtio-fs: tag </dev/null> not found
> Mounting FUSE Control File System...
> [/bin/bash]: [mount -t virtio_fs /dev/null /mnt/virtiofs/ -o tag=myfs] return code=[32], execute failed by [root(uid=0)] from [pts/0 (9.4.90.78)]
>
> And my kernel code is:
> https://github.com/rhvgoyal/linux/commits/virtio-fs-dev-5.1
>
> I wonder if the mount command has been changed?
There was a change that went in last night, I believe the new format is:
mount -t virtio_fs myfs /mnt/virtiofs/
with the tagname going into the device position.
Does that work?
Dave
> Thanks,
> Jun
>
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-07-23 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 8:27 [Virtio-fs] mount failed in virtio_fs dev 5.1 piaojun
2019-07-23 8:31 ` Dr. David Alan Gilbert [this message]
2019-07-23 8:45 ` piaojun
2019-07-23 9:01 ` Dr. David Alan Gilbert
2019-07-23 9:07 ` piaojun
2019-07-23 9:36 ` Dr. David Alan Gilbert
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=20190723083150.GC2719@work-vm \
--to=dgilbert@redhat.com \
--cc=piaojun@huawei.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.