[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegvxHs+MvC3N2Cbocp0UNrM47_GEUSV+mAx=8VVNDz7r_g@mail.gmail.com>
Date: Tue, 19 Jun 2018 16:04:41 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Christoph Hellwig <hch@...radead.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Miklos Szeredi <mszeredi@...hat.com>,
overlayfs <linux-unionfs@...r.kernel.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/39] vfs: export vfs_ioctl() to modules
On Mon, Jun 11, 2018 at 6:24 PM, Christoph Hellwig <hch@...radead.org> wrote:
> On Mon, Jun 11, 2018 at 09:19:01AM +0200, Miklos Szeredi wrote:
>> We don't. Obviously need to make sure to only ever do ioctl's in
>> overlayfs that have a common definition across filesystems. Not a lot
>> of those, luckily...
>
> Which are those? If they are common and possibly called from kernel
> code they should probably be made into methods instead.
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.
Thanks,
Miklos
Powered by blists - more mailing lists