From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757269Ab2JEUAo (ORCPT ); Fri, 5 Oct 2012 16:00:44 -0400 Received: from fieldses.org ([174.143.236.118]:40163 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757235Ab2JEUAj (ORCPT ); Fri, 5 Oct 2012 16:00:39 -0400 Date: Fri, 5 Oct 2012 16:00:09 -0400 From: "J. Bruce Fields" To: Stanislav Kinsbursky Cc: "Eric W. Biederman" , "tglx@linutronix.de" , "mingo@redhat.com" , "davem@davemloft.net" , "hpa@zytor.com" , "thierry.reding@avionic-design.de" , "bfields@redhat.com" , "eric.dumazet@gmail.com" , Pavel Emelianov , "neilb@suse.de" , "netdev@vger.kernel.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "paul.gortmaker@windriver.com" , "viro@zeniv.linux.org.uk" , "gorcunov@openvz.org" , "akpm@linux-foundation.org" , "tim.c.chen@linux.intel.com" , "devel@openvz.org" Subject: Re: [RFC PATCH 0/5] net: socket bind to file descriptor introduced Message-ID: <20121005200009.GA30139@fieldses.org> References: <20120815161141.7598.16682.stgit@localhost.localdomain> <87y5lf7d37.fsf@xmission.com> <50320EE5.10307@parallels.com> <20120904190007.GB29369@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20120904190007.GB29369@fieldses.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 04, 2012 at 03:00:07PM -0400, bfields wrote: > On Mon, Aug 20, 2012 at 02:18:13PM +0400, Stanislav Kinsbursky wrote: > > 16.08.2012 07:03, Eric W. Biederman пишет: > > >Stanislav Kinsbursky writes: > > > > > >>This patch set introduces new socket operation and new system call: > > >>sys_fbind(), which allows to bind socket to opened file. > > >>File to bind to can be created by sys_mknod(S_IFSOCK) and opened by > > >>open(O_PATH). > > >> > > >>This system call is especially required for UNIX sockets, which has name > > >>lenght limitation. > > >> > > >>The following series implements... > > > > > >Hmm. I just realized this patchset is even sillier than I thought. > > > > > >Stanislav is the problem you are ultimately trying to solve nfs clients > > >in a container connecting to the wrong user space rpciod? > > > > > > > Hi, Eric. > > The problem you mentioned was the reason why I started to think about this. > > But currently I believe, that limitations in unix sockets connect or > > bind should be removed, because it will be useful it least for CRIU > > project. > > > > >Aka net/sunrpc/xprtsock.c:xs_setup_local only taking an absolute path > > >and then creating a delayed work item to actually open the unix domain > > >socket? > > > > > >The straight correct and straight forward thing to do appears to be: > > >- Capture the root from current->fs in xs_setup_local. > > >- In xs_local_finish_connect change current->fs.root to the captured > > > version of root before kernel_connect, and restore current->fs.root > > > after kernel_connect. > > > > > >It might not be a bad idea to implement open on unix domain sockets in > > >a filesystem as create(AF_LOCAL)+connect() which would allow you to > > >replace __sock_create + kernel_connect with a simple file_open_root. > > > > > > > I like the idea of introducing new family (AF_LOCAL_AT for example) > > and new sockaddr for connecting or binding from specified root. The > > only thing I'm worrying is passing file descriptor to unix bind or > > connect routine. Because this approach doesn't provide easy way to > > use such family and sockaddr in kernel (like in NFS example). > > > > >But I think the simple scheme of: > > >struct path old_root; > > >old_root = current->fs.root; > > >kernel_connect(...); > > >current->fs.root = old_root; > > > > > >Is more than sufficient and will remove the need for anything > > >except a purely local change to get nfs clients to connect from > > >containers. > > > > > > > That was my first idea. > > So is this what you're planning on doing now? What ever happened to this? --b. > > > And probably it would be worth to change all > > fs_struct to support sockets with relative path. > > What do you think about it? > > I didn't understand the question. Are you suggesting that changes to > fs_struct would be required to make this work? I don't see why. > > --b.