From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-8.cisco.com ([173.37.86.79]:3341 "EHLO rcdn-iport-8.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941AbcEISju (ORCPT ); Mon, 9 May 2016 14:39:50 -0400 Subject: Re: [PATCH] VFS: pass the flag setting by fcntl() to vfs To: Christoph Hellwig References: <20160508104038.GA13657@infradead.org> <20160509070248.GA24065@infradead.org> Cc: Alexander Viro , Jeff Layton , "J. Bruce Fields" , Trond Myklebust , Anna Schumaker , linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, Enke Chen From: Enke Chen Message-ID: Date: Mon, 9 May 2016 11:39:48 -0700 MIME-Version: 1.0 In-Reply-To: <20160509070248.GA24065@infradead.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, Christoph: On 5/9/16 12:02 AM, Christoph Hellwig wrote: > On Sun, May 08, 2016 at 05:50:32PM -0700, Enke Chen wrote: >> As explained in the email, currently the validation of the flags does reach >> the vfs, but the setting does not. > > s/vfs/fs/, and yes, that's intentional. > >> We have an application that uses the FUSE >> to implement a user-space socket, and the flags are needed. > > And that's not a supported use case. > Understood, and that is the reason for the simple patch :-) User-space networking stacks exist for several reasons, e.g., for migrating from micro-kernel based systems, or for avoiding large changes to the networking stack in the kernel. What is the concern with the patch? Regards, -- Enke