From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Jens Axboe <axboe@fb.com>
Cc: Tejun Heo <tj@kernel.org>, Fengguang Wu <fengguang.wu@intel.com>,
lkp@01.org, Philip Li <philip.li@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [writeback] 8bc4ad9498: INFO: suspicious RCU usage. ]
Date: Fri, 9 Sep 2016 08:46:40 +0800 [thread overview]
Message-ID: <20160909004640.GA7334@yexl-desktop> (raw)
In-Reply-To: <4cace953-b5b9-4840-f3f2-b21bd4f30095@fb.com>
On 09/08, Jens Axboe wrote:
>On 09/07/2016 08:04 PM, Ye Xiaolong wrote:
>>On 09/08, Fengguang Wu wrote:
>>>Hi Jens and Tejun,
>>>
>>>>The command line was in the original email:
>>>>
>>>>$ qemu-system-x86_64 -enable-kvm -cpu Westmere -m 512M
>>>>
>>>>And agree, in general it'd be nice if there was a link to the image as
>>>>well, so that folks can reproduce.
>>>
>>>Yes we have a reproduce script internally, however need to polish it
>>>up and make it general usable by kernel developers.
>>>
>>>CC Philip. It'd be helpful to give more priority to the "lkp qemu"
>>>reproduce command.
>>>
>>>For the warning here, it does not depend on any initrd, I just
>>>confirmed this simple script can reproduce the problem.
>>
>>Yes, just confirmed that v4.8-rc5 doesn't have this warning, while kernel
>>for the updated commit (fa0e2cb1af765691fabd329f03cad563a0eebf18) on branch
>>wb-buf-throttle could reproduce it.
>
>Anyone willing to try the below patch?
The warning log is gone with this patch.
Tested-by: Xiaolong Ye <xiaolong.ye@intel.com>
Thanks,
Xiaolong
>
>diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
>index ef61bda76317..a7bb2e6bcaef 100644
>--- a/block/cfq-iosched.c
>+++ b/block/cfq-iosched.c
>@@ -3764,9 +3764,11 @@ static void check_blkcg_changed(struct
>cfq_io_cq *cic, struct bio *bio)
> struct cfq_data *cfqd = cic_to_cfqd(cic);
> struct cfq_queue *cfqq;
> uint64_t serial_nr;
>+ bool nonroot_cg;
>
> rcu_read_lock();
> serial_nr = bio_blkcg(bio)->css.serial_nr;
>+ nonroot_cg = bio_blkcg(bio) != &blkcg_root;
> rcu_read_unlock();
>
> /*
>@@ -3781,7 +3783,7 @@ static void check_blkcg_changed(struct
>cfq_io_cq *cic, struct bio *bio)
> * do proper throttling of writes. Turn off wbt for that
> * case.
> */
>- if (bio_blkcg(bio) != &blkcg_root) {
>+ if (nonroot_cg) {
> struct request_queue *q = cfqd->queue;
>
> if (q->rq_wb)
>
>--
>Jens Axboe
>
prev parent reply other threads:[~2016-09-09 0:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 10:21 [writeback] 8bc4ad9498: INFO: suspicious RCU usage. ] kernel test robot
2016-09-01 20:13 ` Jens Axboe
2016-09-02 14:56 ` Tejun Heo
2016-09-02 15:36 ` Paul E. McKenney
2016-09-02 15:49 ` Jens Axboe
2016-09-02 17:00 ` Paul E. McKenney
2016-09-02 18:00 ` Tejun Heo
2016-09-07 16:41 ` Tejun Heo
2016-09-07 19:25 ` Jens Axboe
2016-09-08 1:43 ` [LKP] " Fengguang Wu
2016-09-08 2:04 ` Ye Xiaolong
2016-09-08 15:52 ` Jens Axboe
2016-09-09 0:46 ` Ye Xiaolong [this message]
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=20160909004640.GA7334@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=axboe@fb.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=philip.li@intel.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).