From: Juergen Gross <jgross@suse.com>
To: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xenproject.org
Cc: Seth Forshee <seth.forshee@canonical.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCHv5 2/2] xenfs: Use proc_create_mount_point() to create /proc/xen
Date: Thu, 17 Nov 2016 14:09:12 +0100 [thread overview]
Message-ID: <45cc7d5f-28a2-122d-3f52-81f4fdb73c20@suse.com> (raw)
In-Reply-To: <1479121976-26568-3-git-send-email-david.vrabel@citrix.com>
On 14/11/16 12:12, David Vrabel wrote:
> From: Seth Forshee <seth.forshee@canonical.com>
>
> Mounting proc in user namespace containers fails if the xenbus
> filesystem is mounted on /proc/xen because this directory fails
> the "permanently empty" test. proc_create_mount_point() exists
> specifically to create such mountpoints in proc but is currently
> proc-internal. Export this interface to modules, then use it in
> xenbus when creating /proc/xen.
>
> Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Applied to xen/tip.git for-linus-4.10
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-11-17 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 11:12 [PATCH v5 0/2] xenfs: xenbus and container related bug fixes David Vrabel
2016-11-14 11:12 ` [PATCHv5 1/2] xenbus: fix deadlock on writes to /proc/xen/xenbus David Vrabel
2016-11-14 11:33 ` Jan Beulich
2016-11-14 11:12 ` [PATCHv5 2/2] xenfs: Use proc_create_mount_point() to create /proc/xen David Vrabel
2016-11-17 13:09 ` Juergen Gross [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=45cc7d5f-28a2-122d-3f52-81f4fdb73c20@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=seth.forshee@canonical.com \
--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).