From: Beau Belgrave <beaub@linux.microsoft.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
dcook@linux.microsoft.com, alanau@linux.microsoft.com,
brauner@kernel.org, akpm@linux-foundation.org,
ebiederm@xmission.com, keescook@chromium.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v9 05/11] tracing/user_events: Add ioctl for disabling addresses
Date: Tue, 28 Mar 2023 14:53:15 -0700 [thread overview]
Message-ID: <20230328215315.GA143@W11-BEAU-MD.localdomain> (raw)
In-Reply-To: <20230328173740.0595c953@gandalf.local.home>
On Tue, Mar 28, 2023 at 05:37:40PM -0400, Steven Rostedt wrote:
> On Tue, 28 Mar 2023 17:32:00 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > > +static long user_events_ioctl_unreg(unsigned long uarg)
> > > +{
> > > + struct user_unreg __user *ureg = (struct user_unreg __user *)uarg;
> > > + struct user_event_mm *mm = current->user_event_mm;
> > > + struct user_event_enabler *enabler, *next;
> > > + struct user_unreg reg;
> > > + long ret;
> > > +
> > > + ret = user_unreg_get(ureg, ®);
> > > +
> > > + if (ret)
> > > + return ret;
> > > +
> > > + if (!mm)
> > > + return -ENOENT;
> > > +
> > > + ret = -ENOENT;
> >
> > Probably should add:
> >
> > if (reg.__reserved || reg.__reserved2)
> > return -EINVAL;
> >
> > here.
Nice catch! Yes I'll add this.
>
> I finished my review.
>
> Can to send a v10 out with this update, and also update all the structs to
> have the fields tabbed out for easier reading.
>
Yep will do, I will have the tabbed out changes in a isolated patch in
the v10 series.
Thanks,
-Beau
> Thanks!
>
> -- Steve
next prev parent reply other threads:[~2023-03-28 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 22:30 [PATCH v9 00/11] tracing/user_events: Remote write ABI Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 01/11] tracing/user_events: Split header into uapi and kernel Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 02/11] tracing/user_events: Track fork/exec/exit for mm lifetime Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 03/11] tracing/user_events: Use remote writes for event enablement Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 04/11] tracing/user_events: Fixup enable faults asyncly Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 05/11] tracing/user_events: Add ioctl for disabling addresses Beau Belgrave
2023-03-28 21:32 ` Steven Rostedt
2023-03-28 21:37 ` Steven Rostedt
2023-03-28 21:53 ` Beau Belgrave [this message]
2023-03-24 22:30 ` [PATCH v9 06/11] tracing/user_events: Update self-tests to write ABI Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 07/11] tracing/user_events: Add ABI self-test Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 08/11] tracing/user_events: Use write ABI in example Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 09/11] tracing/user_events: Update documentation for ABI Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 10/11] tracing/user_events: Charge event allocs to cgroups Beau Belgrave
2023-03-24 22:30 ` [PATCH v9 11/11] tracing/user_events: Limit global user_event count Beau Belgrave
2023-03-26 15:23 ` [PATCH v9 00/11] tracing/user_events: Remote write ABI Masami Hiramatsu
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=20230328215315.GA143@W11-BEAU-MD.localdomain \
--to=beaub@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=alanau@linux.microsoft.com \
--cc=brauner@kernel.org \
--cc=dcook@linux.microsoft.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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