From: David Vrabel <david.vrabel@citrix.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: David Vrabel <david.vrabel@citrix.com>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<xen-devel@lists.xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>
Subject: [PATCH v4 0/3] libfs,xenfs: replace /proc/xen/xenbus with a symlink
Date: Fri, 28 Oct 2016 16:52:36 +0100 [thread overview]
Message-ID: <1477669959-9486-1-git-send-email-david.vrabel@citrix.com> (raw)
Using /proc/xen/xenbus can cause deadlocks on the atomic file position
mutex since this file should behave like a character device and not a
regular file. This is easiest to achive by making it a symlink to the
existing /dev/xen/xenbus device.
This requires extending simple_fill_super() to add symlinks as well as
regular files.
David
Changes in v4:
- Switch on file type in simple_fill_super()
- Make xen_xenus_fops and xen_privcmd_fops static
- Rebased on v4.9-rc2.
- Add patch from Seth for namespace support.
Changes in v3:
- Rebased on v4.7-rc5.
Changes in v2:
- Simplified simple_fill_super() change.
next reply other threads:[~2016-10-28 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 15:52 David Vrabel [this message]
2016-10-28 15:52 ` [PATCHv4 1/3] libfs: allow simple_fill_super() to add symlinks David Vrabel
2016-10-28 15:52 ` [PATCHv4 2/3] xenfs: replace xenbus and privcmd with symlinks David Vrabel
2016-10-28 15:52 ` [PATCHv4 3/3] xenfs: Use proc_create_mount_point() to create /proc/xen David Vrabel
2016-10-28 16:22 ` [PATCH v4 0/3] libfs,xenfs: replace /proc/xen/xenbus with a symlink Al Viro
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=1477669959-9486-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xen-devel@lists.xenproject.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).