From: Chunyan Liu <cyliu@suse.com>
To: qemu-devel@nongnu.org, libvir-list@redhat.com
Cc: Chunyan Liu <cyliu@suse.com>
Subject: [Qemu-devel] [PATCH 0/2] fix: unix sockets created for virtio-serail has insufficient permissions
Date: Tue, 2 Sep 2014 15:40:41 +0800 [thread overview]
Message-ID: <1409643643-31589-1-git-send-email-cyliu@suse.com> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=13078#c11
https://bugzilla.novell.com/show_bug.cgi?id=888166
To use virtio-serial device, unix socket created for chardev with
default umask(022) has insufficient permissions.
e.g.:
-device virtio-serial \
-chardev socket,path=/tmp/foo,server,nowait,id=foo \
-device virtserialport,chardev=foo,name=org.fedoraproject.port.0
#ls -l /tmp/somefile.sock
srwxr-xr-x 1 qemu qemu 0 21. Jul 14:19 /tmp/somefile.sock
Other users in the same group (like real user, test engines, etc)
cannot write to this socket.
These patch series contains a qemu patch and a libvirt patch:
qemu patch: adds a new 'umask' option to -chardev, so that user can
change the umask.
libvirt patch: pass 'umask=0x002' paramter to qemu command line
for virtio-serial device
Chunyan Liu (2):
qemu side: add 'umask' option to chardev
libvirt side: qemu: add umask(002) to virtio-serial chardev commandline
--
1.8.4.5
next reply other threads:[~2014-09-02 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:40 Chunyan Liu [this message]
2014-09-02 7:40 ` [Qemu-devel] [PATCH 1/2] add 'umask' option to -chardev Chunyan Liu
2014-09-02 8:54 ` Daniel P. Berrange
2014-09-02 9:08 ` Chun Yan Liu
2014-09-02 9:16 ` Daniel P. Berrange
2014-09-02 10:05 ` Chun Yan Liu
2014-09-02 10:53 ` Markus Armbruster
2014-09-02 7:40 ` [Qemu-devel] [PATCH 2/2] qemu: add umask(002) to virtio-serial chardev commandline Chunyan Liu
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=1409643643-31589-1-git-send-email-cyliu@suse.com \
--to=cyliu@suse.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.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 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).