[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190805233349.GA27746@ZenIV.linux.org.uk>
Date: Tue, 6 Aug 2019 00:33:49 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Chris Wilson <chris@...is-wilson.co.uk>,
David Howells <dhowells@...hat.com>,
Christoph Hellwig <hch@....de>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCHv2 2/3] i915: convert to new mount API
On Mon, Aug 05, 2019 at 07:12:55PM +0100, Al Viro wrote:
> On Tue, Aug 06, 2019 at 01:03:06AM +0900, Sergey Senozhatsky wrote:
> > tmpfs does not set ->remount_fs() anymore and its users need
> > to be converted to new mount API.
>
> Could you explain why the devil do you bother with remount at all?
> Why not pass the right options when mounting the damn thing?
Incidentally, the only remaining modular user of get_fs_type() is the
same i915_gemfs.c. And I wonder if we should aim for unexporting
the damn thing instead of exporting put_filesystem()...
Note that users in tomoyo and apparmor are bogus - they are in the
instances of ill-defined method that needs to be split and moved,
with the lookups (fs type included) replaced with callers passing
the values they look up and will end up using.
IOW, outside of core VFS we have very few legitimate users, and the
one in kernel/trace might be better off as vfs_submount_by_name().
Powered by blists - more mailing lists