public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: re: rcutorture: Add RCU grace-period performance tests
Date: Wed, 03 Feb 2016 04:34:08 +0000	[thread overview]
Message-ID: <20160203043407.GA32754@mwanda> (raw)

Hello Paul E. McKenney,

This is a semi-automatic email about new static checker warnings.

The patch 7f68f317a3d9: "rcutorture: Add RCU grace-period performance 
tests" from Dec 31, 2015, leads to the following Smatch complaint:

kernel/rcu/rcuperf.c:486 rcu_perf_cleanup()
	 error: we previously assumed 'writer_n_durations' could be null (see line 465)

kernel/rcu/rcuperf.c
   442  static void
   443  rcu_perf_cleanup(void)
   444  {
   445          int i;
   446          int j;
   447          int ngps = 0;
   448          u64 *wdp;
   449          u64 *wdpp;
   450  
   451          if (torture_cleanup_begin())
   452                  return;
   453  
   454          if (reader_tasks) {
   455                  for (i = 0; i < nrealreaders; i++)
   456                          torture_stop_kthread(rcu_perf_reader,
   457                                               reader_tasks[i]);
   458                  kfree(reader_tasks);
   459          }
   460  
   461          if (writer_tasks) {
   462                  for (i = 0; i < nrealwriters; i++) {
   463                          torture_stop_kthread(rcu_perf_writer,
   464						     writer_tasks[i]);
   465				if (!writer_n_durations)
                                     ^^^^^^^^^^^^^^^^^^
Can be NULL here.

   466					continue;
   467				j = writer_n_durations[i];
   468				pr_alert("%s%s writer %d gps: %d\n",
   469					 perf_type, PERF_FLAG, i, j);
   470				ngps += j;
   471			}
   472			pr_alert("%s%s start: %llu end: %llu duration: %llu gps: %d batches: %ld\n",
   473				 perf_type, PERF_FLAG,
   474				 t_rcu_perf_writer_started, t_rcu_perf_writer_finished,
   475				 t_rcu_perf_writer_finished -
   476				 t_rcu_perf_writer_started,
   477				 ngps,
   478				 b_rcu_perf_writer_finished -
   479				 b_rcu_perf_writer_started);
   480			for (i = 0; i < nrealwriters; i++) {
   481				if (!writer_durations)
   482					break;
   483				wdpp = writer_durations[i];
   484				if (!wdpp)
   485					continue;
   486				for (j = 0; j <= writer_n_durations[i]; j++) {
                                                 ^^^^^^^^^^^^^^^^^^^^^
Unchecked dereference.

   487					wdp = &wdpp[j];
   488					pr_alert("%s%s %4d writer-duration: %5d %llu\n",

regards,
dan carpenter

             reply	other threads:[~2016-02-03  4:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03  4:34 Dan Carpenter [this message]
2016-02-03  5:13 ` rcutorture: Add RCU grace-period performance tests Paul E. McKenney
2016-02-03  5:25 ` Dan Carpenter

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=20160203043407.GA32754@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.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