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;
Date:   Tue, 11 Sep 2018 18:11:43 +0200
Message-ID: <s5h7ejsnhds.wl-tiwai@suse.de>
From:   Takashi Iwai <tiwai@suse.de>
To:     Jens Axboe <axboe@kernel.dk>
Cc:     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
In-Reply-To: <8b5a7dc9-2dc1-16ee-4b05-a72eb6680c77@kernel.dk>
References: <s5ha7ooxbps.wl-tiwai@suse.de>
        <8b5a7dc9-2dc1-16ee-4b05-a72eb6680c77@kernel.dk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/26
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 11 Sep 2018 18:09:44 +0200,
Jens Axboe wrote:
> 
> 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?

IIRC, 4.18 worked fine.  Let me see whether I have a backup...


Takashi