mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Kees Cook <keescook@chromium.org>
Cc: Zubin Mithra <zsm@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Guenter Roeck <groeck@chromium.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] tracefs: Annotate tracefs_ops with __ro_after_init
Date: Tue, 24 Jul 2018 18:39:30 -0400	[thread overview]
Message-ID: <20180724183930.1ac4bcd0@gandalf.local.home> (raw)
In-Reply-To: <CAGXu5jJ7jS=ChfVF1oRJsGu-bSXK_WvTs94f_dQ9ud9Bt81-WA@mail.gmail.com>

On Tue, 24 Jul 2018 15:07:18 -0700
Kees Cook <keescook@chromium.org> wrote:

> Adding Steven (maintainer) and Al (fs) to CC...

Thanks, first I've seen of this.

> 
> On Tue, Jul 24, 2018 at 1:02 PM, Zubin Mithra <zsm@chromium.org> wrote:
> > tracefs_ops is initialized inside tracefs_create_instance_dir and not
> > modified after. tracefs_create_instance_dir allows for initialization
> > only once, and is called from create_trace_instances(marked __init),
> > which is called from tracer_init_tracefs(marked __init).

Then, especially with this change, we should mark
tracefs_create_instance_dir() as init, as it would fail any other time.

> >
> > Signed-off-by: Zubin Mithra <zsm@chromium.org>
> > Reviewed-by: Kees Cook <keescook@chromium.org>  
> 
> Who's tree should this go through?

I can take it or someone else can, and I'll ack it if need be.

-- Steve


> 
> Thanks!
> 
> -Kees
> 
> > ---
> >  fs/tracefs/inode.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/tracefs/inode.c b/fs/tracefs/inode.c
> > index bea8ad876bf9..20e965873f27 100644
> > --- a/fs/tracefs/inode.c
> > +++ b/fs/tracefs/inode.c
> > @@ -53,7 +53,7 @@ static const struct file_operations tracefs_file_operations = {
> >  static struct tracefs_dir_ops {
> >         int (*mkdir)(const char *name);
> >         int (*rmdir)(const char *name);
> > -} tracefs_ops;
> > +} tracefs_ops __ro_after_init;
> >
> >  static char *get_dname(struct dentry *dentry)
> >  {
> > --
> > 2.18.0.233.g985f88cf7e-goog
> >  
> 
> 
> 


      reply	other threads:[~2018-07-24 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 20:02 Zubin Mithra
2018-07-24 22:07 ` Kees Cook
2018-07-24 22:39   ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180724183930.1ac4bcd0@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=groeck@chromium.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zsm@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®