From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753631AbdK3Qn1 (ORCPT ); Thu, 30 Nov 2017 11:43:27 -0500 Received: from mga09.intel.com ([134.134.136.24]:5830 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753588AbdK3QnZ (ORCPT ); Thu, 30 Nov 2017 11:43:25 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,341,1508828400"; d="scan'208";a="8947840" Date: Thu, 30 Nov 2017 18:43:21 +0200 From: Jarkko Sakkinen To: Christoph Hellwig Cc: platform-driver-x86@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, Alexander Viro , "open list:FILESYSTEMS (VFS and infrastructure)" Subject: Re: [PATCH v6 09/11] fs/pipe.c: export create_pipe_files() and replace_fd() Message-ID: <20171130164321.juvn67pu4jrjq76j@linux.intel.com> References: <20171125193132.24321-1-jarkko.sakkinen@linux.intel.com> <20171125193132.24321-10-jarkko.sakkinen@linux.intel.com> <20171128143504.GA22918@infradead.org> <20171128204220.j7ipouoyhsbvm7zk@linux.intel.com> <20171128210551.GA12431@infradead.org> <20171128215753.qnu5krswowjq6gwn@linux.intel.com> <20171129231357.GA23443@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171129231357.GA23443@infradead.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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