[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiqUibNm0W-KcCb3H+aiSVr4Uz3COZq=LjqGd__6guFEg@mail.gmail.com>
Date: Wed, 5 Feb 2025 08:06:29 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Christian Brauner <brauner@...nel.org>, Jeff Layton <jlayton@...nel.org>,
David Howells <dhowells@...hat.com>, "Gautham R. Shenoy" <gautham.shenoy@....com>,
K Prateek Nayak <kprateek.nayak@....com>, Mateusz Guzik <mjguzik@...il.com>,
Neeraj Upadhyay <Neeraj.Upadhyay@....com>, Oliver Sang <oliver.sang@...el.com>,
Swapnil Sapkal <swapnil.sapkal@....com>, WangYuli <wangyuli@...ontech.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] pipe: introduce struct file_operations pipeanon_fops
On Wed, 5 Feb 2025 at 07:34, Oleg Nesterov <oleg@...hat.com> wrote:
>
> So that fifos and anonymous pipes could have different f_op methods.
> Preparation to simplify the next patch.
Looks good, except:
> +++ b/fs/internal.h
> extern const struct file_operations pipefifo_fops;
> +extern const struct file_operations pipeanon_fops;
I think this should just be 'static' to inside fs/pipe.c, no?
The only reason pipefifo_fops is in that header is because it's used
for named pipes outside the pipe code, in init_special_inode().
So I don't think pipeanon_fops should be exposed anywhere outside fs/pipe.c.
Linus
Powered by blists - more mailing lists