From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 07/39] vfs: export vfs_ioctl() to modules Date: Tue, 19 Jun 2018 15:54:51 +0100 Message-ID: <20180619145451.GQ30522@ZenIV.linux.org.uk> References: <20180529144339.16538-1-mszeredi@redhat.com> <20180529144339.16538-8-mszeredi@redhat.com> <20180604084904.GF11333@infradead.org> <20180610045657.GM30522@ZenIV.linux.org.uk> <20180611162412.GA7574@infradead.org> <20180619142421.GA16151@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Miklos Szeredi Cc: Christoph Hellwig , Miklos Szeredi , overlayfs , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-unionfs@vger.kernel.org On Tue, Jun 19, 2018 at 04:34:33PM +0200, Miklos Szeredi wrote: > On Tue, Jun 19, 2018 at 4:24 PM, Christoph Hellwig wrote: > > On Tue, Jun 19, 2018 at 04:04:41PM +0200, Miklos Szeredi wrote: > >> FS_IOC* > >> > >> Haven't looked deeply. For now overlayfs just implements > >> FS_IOC_{GET|SET}FLAGS because some of these flags are quite generic > >> and implementing them on the overlay is easy. > >> > >> Yes, turning into a method makes sense. > > > > Do you want to do this or should I send a patch? > > Do it. You are much more familiar with regular fs that implement > these ioctls. Untangling overlap between FS_IOC_...FLAGS and > FS_IOC_...XATTR looks "interesting". Suggestion: have that go through ->setattr(); that's what ATTR_ATTR_FLAG was supposed to be for, IIRC.