From: Dan Carpenter <dan.carpenter@oracle.com>
To: paolo.valente@linaro.org
Cc: linux-block@vger.kernel.org
Subject: [bug report] block, bfq: update blkio stats outside the scheduler lock
Date: Wed, 3 Apr 2019 09:15:12 +0300 [thread overview]
Message-ID: <20190403061512.GA1618@kadam> (raw)
Hello Paolo Valente,
This is a semi-automatic email about new static checker warnings.
The patch 24bfd19bb789: "block, bfq: update blkio stats outside the
scheduler lock" from Nov 13, 2017, leads to the following Smatch
complaint:
block/bfq-iosched.c:5013 __bfq_insert_request()
error: we previously assumed 'bfqq' could be null (see line 5008)
block/bfq-iosched.c
5007
5008 waiting = bfqq && bfq_bfqq_wait_request(bfqq);
^^^^
The patch adds a NULL check here. Hopefully it's not required because
5009 bfq_add_request(rq);
5010 idle_timer_disabled = waiting && !bfq_bfqq_wait_request(bfqq);
5011
5012 rq->fifo_time = ktime_get_ns() + bfqd->bfq_fifo_expire[rq_is_sync(rq)];
5013 list_add_tail(&rq->queuelist, &bfqq->fifo);
^^^^^^^^^^^
the existing code assumes "bfqq" is valid.
5014
5015 bfq_rq_enqueued(bfqd, bfqq, rq);
regards,
dan carpenter
reply other threads:[~2019-04-03 6:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190403061512.GA1618@kadam \
--to=dan.carpenter@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=paolo.valente@linaro.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