From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Gabriele Paoloni <gpaoloni@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>,
Tao Zhou <tao.zhou@linux.dev>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH V6 01/16] rv: Add Runtime Verification (RV) interface
Date: Wed, 20 Jul 2022 11:21:02 -0400 [thread overview]
Message-ID: <20220720112102.32415cc7@gandalf.local.home> (raw)
In-Reply-To: <69bb4c369b4f6f12014eb9ca3c28b74e4378c007.1658244826.git.bristot@kernel.org>
On Tue, 19 Jul 2022 19:27:06 +0200
Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
> +/*
> + * enabled_monitors interface.
> + */
Doesn't the rv_monitors_list need to be protected by the rv_interface_lock
mutex?
> +static void disable_all_monitors(void)
> +{
> + struct rv_monitor_def *mdef;
> +
I think you need:
mutex_lock(&rv_interface_lock);
> + list_for_each_entry(mdef, &rv_monitors_list, list)
> + disable_monitor(mdef);
mutex_unlock(&rv_interface_lock);
> +}
> +
> +static int enabled_monitors_open(struct inode *inode, struct file *file)
> +{
As this gets called directly from the open system call.
> + if ((file->f_mode & FMODE_WRITE) && (file->f_flags & O_TRUNC))
> + disable_all_monitors();
> +
> + return seq_open(file, &enabled_monitors_seq_ops);
> +};
> +
[..]
> +
> +static const struct file_operations enabled_monitors_ops = {
> + .open = enabled_monitors_open,
Here.
-- Steve
> + .read = seq_read,
> + .write = enabled_monitors_write,
> + .llseek = seq_lseek,
> + .release = seq_release,
> +};
next prev parent reply other threads:[~2022-07-20 15:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 17:27 [PATCH V6 00/16] The Runtime Verification (RV) interface Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 01/16] rv: Add " Daniel Bristot de Oliveira
2022-07-20 14:47 ` Steven Rostedt
2022-07-20 15:20 ` Daniel Bristot de Oliveira
2022-07-20 15:21 ` Steven Rostedt [this message]
2022-07-20 15:33 ` Daniel Bristot de Oliveira
2022-07-21 14:38 ` Tao Zhou
2022-07-21 14:54 ` Steven Rostedt
2022-07-19 17:27 ` [PATCH V6 02/16] rv: Add runtime reactors interface Daniel Bristot de Oliveira
2022-07-20 16:41 ` Steven Rostedt
2022-07-20 16:50 ` Daniel Bristot de Oliveira
2022-07-20 17:02 ` Steven Rostedt
2022-07-20 17:37 ` Daniel Bristot de Oliveira
2022-07-20 17:45 ` Steven Rostedt
2022-07-21 14:46 ` Tao Zhou
2022-07-19 17:27 ` [PATCH V6 03/16] rv/include: Add helper functions for deterministic automata Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 04/16] rv/include: Add deterministic automata monitor definition via C macros Daniel Bristot de Oliveira
2022-07-20 20:06 ` Steven Rostedt
2022-07-21 12:08 ` Daniel Bristot de Oliveira
2022-07-21 13:59 ` Steven Rostedt
2022-07-21 16:38 ` Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 05/16] rv/include: Add instrumentation helper functions Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 06/16] Documentation/rv: Add a basic documentation Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 07/16] tools/rv: Add dot2c Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 08/16] Documentation/rv: Add deterministic automaton documentation Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 09/16] tools/rv: Add dot2k Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 10/16] Documentation/rv: Add deterministic automata monitor synthesis documentation Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 11/16] Documentation/rv: Add deterministic automata instrumentation documentation Daniel Bristot de Oliveira
2022-07-21 14:57 ` Tao Zhou
2022-07-19 17:27 ` [PATCH V6 12/16] rv/monitor: Add the wip monitor skeleton created by dot2k Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 13/16] rv/monitor: Add the wip monitor Daniel Bristot de Oliveira
2022-07-19 17:27 ` [PATCH V6 14/16] rv/monitor: Add the wwnr monitor Daniel Bristot de Oliveira
2022-07-24 18:12 ` kernel test robot
2022-07-19 17:27 ` [PATCH V6 15/16] rv/reactor: Add the printk reactor Daniel Bristot de Oliveira
2022-07-21 15:29 ` Steven Rostedt
2022-07-19 17:27 ` [PATCH V6 16/16] rv/reactor: Add the panic reactor Daniel Bristot de Oliveira
2022-07-21 15:31 ` Steven Rostedt
2022-07-21 16:43 ` Daniel Bristot de Oliveira
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=20220720112102.32415cc7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gpaoloni@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tao.zhou@linux.dev \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=williams@redhat.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).