[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171130164321.juvn67pu4jrjq76j@linux.intel.com>
Date: Thu, 30 Nov 2017 18:43:21 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: platform-driver-x86@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH v6 09/11] fs/pipe.c: export create_pipe_files() and
replace_fd()
On Wed, Nov 29, 2017 at 03:13:57PM -0800, Christoph Hellwig wrote:
> On Tue, Nov 28, 2017 at 11:57:53PM +0200, Jarkko Sakkinen wrote:
> > > Yes. You still shall not play nasty games with file descriptors.
> >
> > I need to put something to file descriptors in order to have a IO
> > channels for the launch enclave hosting process.
>
> Just do it like any other program - open it from your userspace
> program using open() and related syscalls.
In this case it would not work as the launch enclave is still part of
the kernel and it would create a dependency how the user space defines
paths. If using pipe specifically is an issue, I could easily use shmem
file as a mean for communiation.
The way I implemented is much like how I did arch/x86/realmode with HPA
and it has kind of comparable requirements, part of the kernel but not
exactly code living in the kernel namespace.
/Jarkko
Powered by blists - more mailing lists