From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Tao Zhou <tao.zhou@linux.dev>
Cc: Steven Rostedt <rostedt@goodmis.org>,
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>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH V5 01/16] rv: Add Runtime Verification (RV) interface
Date: Fri, 15 Jul 2022 13:47:28 +0200 [thread overview]
Message-ID: <3758d3bd-7272-e907-a51a-44a21d757674@kernel.org> (raw)
In-Reply-To: <Ys/J5fLaojYeiVzL@geo.homenetwork>
On 7/14/22 09:46, Tao Zhou wrote:
> On Wed, Jul 13, 2022 at 11:17:17PM +0200,
> Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
>
> [...]
>
>> +void put_task_monitor_slot(int slot)
>> +{
>> + lockdep_assert_held(&rv_interface_lock);
>> +
>> + if (slot < 0 || slot > RV_PER_TASK_MONITORS) {
>
> slot is the array index that should be 0 here. The up bound is not bigger
> than 0 because the element of array now is RV_PER_TASK_MONITORS.
>
> So up bound check is 'slot > RV_PER_TASK_MONITORS-1'.
fixed! (slot >= RV...)
> [...]
>
>> +/*
>> + * interface for enabling/disabling a monitor.
>> + */
>> +static ssize_t monitor_enable_write_data(struct file *filp, const char __user *user_buf,
>> + size_t count, loff_t *ppos)
>> +{
>> + struct rv_monitor_def *mdef = filp->private_data;
>> + int retval;
>> + bool val;
>> +
>> + retval = kstrtobool_from_user(user_buf, count, &val);
>> + if (retval)
>> + return retval;
>> +
>> + retval = count;
>> +
>> + mutex_lock(&rv_interface_lock);
>> +
>> + if (val)
>> + retval = enable_monitor(mdef);
>> + else
>> + retval = disable_monitor(mdef);
>> +
>> + mutex_unlock(&rv_interface_lock);
>> +
>> + return retval ? retval : count;
>
> Feel that this can be written `return retval ? : count;`
why not...
> [...]
>
>> +static void *enabled_monitors_start(struct seq_file *m, loff_t *pos)
>> +{
>> + struct rv_monitor_def *m_def;
>> + loff_t l;
>> +
>> + mutex_lock(&rv_interface_lock);
>> +
>> + if (list_empty(&rv_monitors_list))
>> + return NULL;
>> +
>> + m_def = list_entry(&rv_monitors_list, struct rv_monitor_def, list);
>> +
>> + for (l = 0; l <= *pos; ) {
>> + m_def = enabled_monitors_next(m, m_def, &l);
>> + if (!m_def)
>> + break;
>
> Is this check is inversed. enabled_monitors_start() will stop at first
> enabled monitor, then enabled_monitors_next() do loop to next. Check
> like the above, enabled_monitors_start() will loop to the last monitor.
> But I doubt myself I do not mention/see it. Sorry for these.
>
> the check is:
>
> if (m_def)
> break;
>
> [...]
see kernel/trace/trace_events.c:s_start...
>> +static ssize_t
>> +enabled_monitors_write(struct file *filp, const char __user *user_buf,
>> + size_t count, loff_t *ppos)
>> +{
>> + char buff[MAX_RV_MONITOR_NAME_SIZE + 2];
>> + struct rv_monitor_def *mdef;
>> + int retval = -EINVAL;
>> + bool enable = true;
>> + char *ptr = buff;
>> + int len;
>> +
>> + if (count < 1 || count > MAX_RV_MONITOR_NAME_SIZE + 2)
>
> @count would not include '\0'. That the max val of @count is
> MAX_RV_MONITOR_NAME_SIZE+1. So the up bound check of @count is
> `count > MAX_RV_MONITOR_NAME_SIZE + 1`.
Fixed for v6...
-- Daniel
next prev parent reply other threads:[~2022-07-15 11:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 21:17 [PATCH V5 00/16] The Runtime Verification (RV) interface Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 01/16] rv: Add " Daniel Bristot de Oliveira
2022-07-14 7:46 ` Tao Zhou
2022-07-15 11:47 ` Daniel Bristot de Oliveira [this message]
2022-07-15 13:48 ` Tao Zhou
2022-07-13 21:17 ` [PATCH V5 02/16] rv: Add runtime reactors interface Daniel Bristot de Oliveira
2022-07-17 15:29 ` Tao Zhou
2022-07-17 18:56 ` kernel test robot
2022-07-13 21:17 ` [PATCH V5 03/16] rv/include: Add helper functions for deterministic automata Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 04/16] rv/include: Add deterministic automata monitor definition via C macros Daniel Bristot de Oliveira
2022-07-17 15:18 ` Tao Zhou
2022-07-18 7:54 ` Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 05/16] rv/include: Add instrumentation helper functions Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 06/16] Documentation/rv: Add a basic documentation Daniel Bristot de Oliveira
2022-07-17 15:19 ` Tao Zhou
2022-07-13 21:17 ` [PATCH V5 07/16] tools/rv: Add dot2c Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 08/16] Documentation/rv: Add deterministic automaton documentation Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 09/16] tools/rv: Add dot2k Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 10/16] Documentation/rv: Add deterministic automata monitor synthesis documentation Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 11/16] Documentation/rv: Add deterministic automata instrumentation documentation Daniel Bristot de Oliveira
2022-07-17 15:20 ` Tao Zhou
2022-07-13 21:17 ` [PATCH V5 12/16] rv/monitor: Add the wip monitor skeleton created by dot2k Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 13/16] rv/monitor: Add the wip monitor Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 14/16] rv/monitor: Add the wwnr monitor Daniel Bristot de Oliveira
2022-07-13 21:17 ` [PATCH V5 15/16] rv/reactor: Add the printk reactor Daniel Bristot de Oliveira
2022-07-17 23:52 ` kernel test robot
2022-07-18 8:45 ` kernel test robot
2022-07-13 21:17 ` [PATCH V5 16/16] rv/reactor: Add the panic reactor Daniel Bristot de Oliveira
2022-07-18 2:05 ` kernel test robot
2022-07-18 11:50 ` kernel test robot
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=3758d3bd-7272-e907-a51a-44a21d757674@kernel.org \
--to=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=rostedt@goodmis.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).