public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"shli@fb.com" <shli@fb.com>
Subject: Re: [PATCH] blk-throttle: Suppress a compiler warning
Date: Thu, 20 Apr 2017 09:43:27 -0600	[thread overview]
Message-ID: <dcbefc9e-05eb-b2cd-bea1-6878c96b7fbf@kernel.dk> (raw)
In-Reply-To: <1492702586.2642.5.camel@sandisk.com>

On 04/20/2017 09:36 AM, Bart Van Assche wrote:
> On Wed, 2017-04-19 at 18:09 -0600, Jens Axboe wrote:
>> On 04/19/2017 05:55 PM, Bart Van Assche wrote:
>>> Avoid that the following warning is reported when building with
>>> W=1 and with CONFIG_BLK_DEV_THROTTLING_LOW=n:
>>>
>>> block/blk-throttle.c: In function ‘blk_throtl_bio’:
>>> block/blk-throttle.c:2042:6: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
>>>   int ret;
>>>       ^~~
>>>
>>> Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
>>> Cc: Shaohua Li <shli@fb.com>
>>> ---
>>>  block/blk-throttle.c | 4 ++++
>>>  1 file changed, 4 insertions(+)
>>>
>>> diff --git a/block/blk-throttle.c b/block/blk-throttle.c
>>> index c82bf9b1fe72..9081ed9a5345 100644
>>> --- a/block/blk-throttle.c
>>> +++ b/block/blk-throttle.c
>>> @@ -2059,6 +2059,10 @@ bool blk_throtl_bio(struct request_queue *q, struct blkcg_gq *blkg,
>>>  	if (ret == 0 || ret == -EBUSY)
>>>  		bio->bi_cg_private = tg;
>>>  	blk_stat_set_issue(&bio->bi_issue_stat, bio_sectors(bio));
>>> +#else
>>> +	/* Avoid that the compiler complains about not using ret */
>>> +	if (ret) {
>>> +	}
>>>  #endif
>>
>> Ugh, that may get rid of the warning, but it does not help on
>> the readability or the ifdefs. How about something like the below?
>> Naming could probably be improved...
>>
>>
>> diff --git a/block/blk-throttle.c b/block/blk-throttle.c
>> index c82bf9b1fe72..b78db2e5fdff 100644
>> --- a/block/blk-throttle.c
>> +++ b/block/blk-throttle.c
>> @@ -2030,6 +2030,20 @@ static inline void throtl_update_latency_buckets(struct throtl_data *td)
>>  }
>>  #endif
>>  
>> +static void blk_throtl_assoc_bio(struct throtl_grp *tg, struct bio *bio)
>> +{
>> +#ifdef CONFIG_BLK_DEV_THROTTLING_LOW
>> +	int ret;
>> +
>> +	ret = bio_associate_current(bio);
>> +	if (ret == 0 || ret == -EBUSY)
>> +		bio->bi_cg_private = tg;
>> +	blk_stat_set_issue(&bio->bi_issue_stat, bio_sectors(bio));
>> +#else
>> +	bio_associate_current(bio);
>> +#endif
>> +}
>> +
>>  bool blk_throtl_bio(struct request_queue *q, struct blkcg_gq *blkg,
>>  		    struct bio *bio)
>>  {
>> @@ -2039,7 +2053,6 @@ bool blk_throtl_bio(struct request_queue *q, struct blkcg_gq *blkg,
>>  	bool rw = bio_data_dir(bio);
>>  	bool throttled = false;
>>  	struct throtl_data *td = tg->td;
>> -	int ret;
>>  
>>  	WARN_ON_ONCE(!rcu_read_lock_held());
>>  
>> @@ -2054,12 +2067,7 @@ bool blk_throtl_bio(struct request_queue *q, struct blkcg_gq *blkg,
>>  	if (unlikely(blk_queue_bypass(q)))
>>  		goto out_unlock;
>>  
>> -	ret = bio_associate_current(bio);
>> -#ifdef CONFIG_BLK_DEV_THROTTLING_LOW
>> -	if (ret == 0 || ret == -EBUSY)
>> -		bio->bi_cg_private = tg;
>> -	blk_stat_set_issue(&bio->bi_issue_stat, bio_sectors(bio));
>> -#endif
>> +	blk_throtl_assoc_bio(tg, bio);
>>  	blk_throtl_update_idletime(tg);
>>  
>>  	sq = &tg->service_queue;
>>
> 
> Hello Jens,
> 
> The above patch looks fine to me. Do you want to queue this patch with
> my Reviewed-by or do you prefer that I post the above as a v2?

Thanks for checking, I'll just add it with your reviewed/reported-by
tags.

-- 
Jens Axboe

      reply	other threads:[~2017-04-20 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 23:55 [PATCH] blk-throttle: Suppress a compiler warning Bart Van Assche
2017-04-20  0:09 ` Jens Axboe
2017-04-20 15:36   ` Bart Van Assche
2017-04-20 15:43     ` Jens Axboe [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=dcbefc9e-05eb-b2cd-bea1-6878c96b7fbf@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Bart.VanAssche@sandisk.com \
    --cc=linux-block@vger.kernel.org \
    --cc=shli@fb.com \
    /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