[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACVxJT88zLoekiwFxq1rdDEnFxPnpZeDYHOWEVQEwHZvFdOy4A@mail.gmail.com>
Date: Fri, 10 Nov 2017 12:26:30 +0200
From: Alexey Dobriyan <adobriyan@...il.com>
To: Djalal Harouni <tixxdz@...il.com>
Cc: Kees Cook <keescook@...omium.org>, Alexey Gladkov <gladkov.alexey@...il.com>,
Andy Lutomirski <luto@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-hardening@...ts.openwall.com, linux-security-module@...r.kernel.org,
linux-api@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>, Akinobu Mita <akinobu.mita@...il.com>, me@...in.cc,
Oleg Nesterov <oleg@...hat.com>, Jeff Layton <jlayton@...chiereds.net>,
Ingo Molnar <mingo@...nel.org>, ebiederm@...ssion.com,
Linus Torvalds <torvalds@...ux-foundation.org>, Daniel Micay <danielmicay@...il.com>,
Jonathan Corbet <corbet@....net>, bfields@...ldses.org,
Stephen Rothwell <sfr@...b.auug.org.au>, solar@...nwall.com
Subject: Re: [PATCH RFC v3 1/7] proc: add proc_fs_info struct to store proc information
On 11/9/17, Djalal Harouni <tixxdz@...il.com> wrote:
> +struct proc_fs_info {
> + struct pid_namespace *pid_ns;
> +};
> +static inline struct proc_fs_info *proc_sb(struct super_block *sb)
> +{
> + return sb->s_fs_info;
> +}
Can you rename this to "struct proc_super_block *" then?
That "info" suffix all over filesystems doesn't add much info itself
just more typing.
Ditto for "fs_info" identifiers.
> +extern inline struct proc_fs_info *proc_sb(struct super_block *sb)
> { return NULL;}
extern inline?
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
