Linux block layer
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Takashi Iwai <tiwai@suse.de>,
	 Paolo Valente <paolo.valente@linaro.org>,
	 linux-block@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] bfq probe failed on 4.19-rc3
Date: Tue, 11 Sep 2018 12:57:48 -0400	[thread overview]
Message-ID: <x491sa0j7jn.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <8d5f3ab2-50e8-226c-8ccb-c722872910db@kernel.dk> (Jens Axboe's message of "Tue, 11 Sep 2018 10:54:19 -0600")

Jens Axboe <axboe@kernel.dk> writes:

>> And then there were 4...
>
> Exactly. I'd bump it to 5 to leave room for one more, if we have to grow it
> again, probably worth it to make it dynamic. So for, not really needed. Takashi,
> can verify that the below fixes it up for you?
>

You can slap a

Reviewed-by: Jeff Moyer <jmoyer@redhat.com>

on that when you commit it.

Cheers,
Jeff

>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index c19f9078da1e..c630e02836a8 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -1510,8 +1510,10 @@ int blkcg_policy_register(struct blkcg_policy *pol)
>  	for (i = 0; i < BLKCG_MAX_POLS; i++)
>  		if (!blkcg_policy[i])
>  			break;
> -	if (i >= BLKCG_MAX_POLS)
> +	if (i >= BLKCG_MAX_POLS) {
> +		pr_warn("blkcg_policy_register: BLKCG_MAX_POLS too small\n");
>  		goto err_unlock;
> +	}
>  
>  	/* Make sure cpd/pd_alloc_fn and cpd/pd_free_fn in pairs */
>  	if ((!pol->cpd_alloc_fn ^ !pol->cpd_free_fn) ||
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index d6869e0e2b64..6980014357d4 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -54,7 +54,7 @@ struct blk_stat_callback;
>   * Maximum number of blkcg policies allowed to be registered concurrently.
>   * Defined here to simplify include dependency.
>   */
> -#define BLKCG_MAX_POLS		3
> +#define BLKCG_MAX_POLS		5
>  
>  typedef void (rq_end_io_fn)(struct request *, blk_status_t);

  reply	other threads:[~2018-09-11 16:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 16:03 [REGRESSION] bfq probe failed on 4.19-rc3 Takashi Iwai
2018-09-11 16:09 ` Jens Axboe
2018-09-11 16:11   ` Takashi Iwai
2018-09-11 16:16     ` Takashi Iwai
2018-09-11 16:20       ` Jens Axboe
2018-09-11 16:48   ` Jeff Moyer
2018-09-11 16:49     ` Jens Axboe
2018-09-11 16:51       ` Jeff Moyer
2018-09-11 16:54         ` Jens Axboe
2018-09-11 16:57           ` Jeff Moyer [this message]
2018-09-11 16:59             ` Jens Axboe
2018-09-12  8:58           ` Takashi Iwai
2018-09-12 14:31             ` Jens Axboe

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=x491sa0j7jn.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=tiwai@suse.de \
    /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