[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whXq_149rcDv9ENkKeKpcEQ93MAvcmAOAbU8=bWG55X2A@mail.gmail.com>
Date: Thu, 9 Jul 2020 11:07:08 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Christoph Hellwig <hch@....de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>, Song Liu <song@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>, linux-raid@...r.kernel.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 15/17] initramfs: switch initramfs unpacking to struct
file based APIs
On Thu, Jul 9, 2020 at 8:18 AM Christoph Hellwig <hch@....de> wrote:
>
> There is no good reason to mess with file descriptors from in-kernel
> code, switch the initramfs unpacking to struct file based write
> instead. As we don't have nice helper for chmod or chown on a struct
> file or struct path use the pathname based ones instead there. This
> causes additional (cached) lookups, but keeps the code much simpler.
This is the only one I'm not a huge fan of.
I agree about moving to 'struct file'. But then you could just do the
chown/chmod using chown/chmod_common() on file->f_path.
That would keep the same semantics, and it feels like a more
straightforward patch.
It would still remove the nasty ksys_fchmod/fchmod, it would just
require our - already existing - *_common() functions to be non-static
(and maybe renamed to "vfs_chown/chmod()" instead, that "*_common()"
naming looks a bit odd compared to all our other "vfs_operation()"
helpers).
Linus
Powered by blists - more mailing lists