Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [REGRESSION] bfq probe failed on 4.19-rc3
To:     Takashi Iwai <tiwai@suse.de>,
        Paolo Valente <paolo.valente@linaro.org>
Cc:     linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
References: <s5ha7ooxbps.wl-tiwai@suse.de>
From:   Jens Axboe <axboe@kernel.dk>
Message-ID: <8b5a7dc9-2dc1-16ee-4b05-a72eb6680c77@kernel.dk>
Date:   Tue, 11 Sep 2018 10:09:44 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <s5ha7ooxbps.wl-tiwai@suse.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 9/11/18 10:03 AM, Takashi Iwai wrote:
> Hi,
> 
> I noticed that bfq doesn't appear in the I/O scheduler list on
> 4.19-rc3.  It seems that blkcg_policy_register() at the beginning of
> bfq_init() returns -ENOSPC, hence the probe aborts silently.
> 
> Is this already addressed?

Haven't heard about this one before. What kernel did you last use that
worked?

-- 
Jens Axboe