Received: by 10.223.176.5 with SMTP id f5csp403761wra; Tue, 6 Feb 2018 00:39:34 -0800 (PST) X-Google-Smtp-Source: AH8x224oyFK3fIbIYdJwAJEPPTZ/35kQ0Tuh+afUmdmDMnpaBhCrsN+2oChusoVN7Je97Wo8KFFf X-Received: by 2002:a17:902:8307:: with SMTP id bd7-v6mr1620102plb.369.1517906374655; Tue, 06 Feb 2018 00:39:34 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1517906374; cv=pass; d=google.com; s=arc-20160816; b=YuQUs6Hm9ZKiOZlqyDCbvpWE/Q6arb8rDbNfRUpB8O+yoSd5tJkxUwwZXhe8lwJ0A6 7EwiBSzHy5xagUN2WjhxJUXvepkyfCzkoqE481A6h77g+KhRldRGo1TNoIao5ADgXruD KvYmJYN0RV84k2Qsc8C5jZkt4U1iMVW3WKh91j5l6j3ub9KUJNDNdKfu972fpmXPPDKP elF2KIUjoWhcvuIRI0Z7TixdkD+F81sVgnXcosYTxBiB0oFgcfwsereDDJFTJLgNHnD4 UI49O+J+vvue9Upl0H7JWGTuQ2I5boSYZXgI3FurNP2EcUPKyIdGQsNWxcjFqmJQ12YK S5/A== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:arc-authentication-results :arc-message-signature:user-agent:message-id:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :dmarc-filter:arc-authentication-results; bh=DS1yzaNWEXIeXIAQMKBdmxokxpQy1g0dY2lYmXdTRBI=; b=vUFYVjsKx3MvgdDADIj1SEpv6OhPi2MeNeD/JN8fsRpXADI78Q2uKSIyKvq8UFU3d5 CYut0dCtRT6yMjF85zrOqKL11hAOXVjzZHR9SrDpn7b30RUtGCs83AAvwehGQv8n0zcn 7XcfNktznY902M0zyd5DlXjZ98vSXMFUBF1usE2mOiz2BsZ3heXxIP2AfphWRuLsUNKk 8GEHTKOB6QNboQNGmNCM1p+kveXxBxJQhBjq/kmSUDagJZbJU4CBaQSfbw9KsYQ3jP6H D+jzXSjOTjFyy2cg2sF7GY/mOGYUVp0G55M753EUVjE4ZbV3oCdbBr4oEJeE61zf9WVD dLcA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@natalenko.name header.s=dkim-20170712 header.b=JMyvtqXf; arc=pass (i=1); spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=natalenko.name Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g3-v6si1302225plp.38.2018.02.06.00.39.19; Tue, 06 Feb 2018 00:39:34 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@natalenko.name header.s=dkim-20170712 header.b=JMyvtqXf; arc=pass (i=1); spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=natalenko.name Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752302AbeBFIiC (ORCPT + 99 others); Tue, 6 Feb 2018 03:38:02 -0500 Received: from vulcan.natalenko.name ([104.207.131.136]:43192 "EHLO vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751835AbeBFIhy (ORCPT ); Tue, 6 Feb 2018 03:37:54 -0500 Received: from mail.natalenko.name (vulcan.natalenko.name [IPv6:2001:19f0:6c00:8846:5400:ff:fe0c:dfa0]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vulcan.natalenko.name (Postfix) with ESMTPSA id E8DF92E595B; Tue, 6 Feb 2018 09:37:52 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.2 vulcan.natalenko.name E8DF92E595B Authentication-Results: vulcan.natalenko.name; dmarc=fail (p=none dis=none) header.from=natalenko.name MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 06 Feb 2018 09:37:52 +0100 From: Oleksandr Natalenko To: Mike Galbraith Cc: Paolo Valente , Jens Axboe , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, ulf.hansson@linaro.org, broonie@kernel.org, linus.walleij@linaro.org, bfq-iosched@googlegroups.com, alban.browaeys@gmail.com, ming.lei@redhat.com, ivan@ludios.org, 169364@studenti.unimore.it, Serena Ziviani Subject: Re: [PATCH BUGFIX 1/1] block, bfq: add requeue-request hook In-Reply-To: <1517903761.9843.12.camel@gmx.de> References: <20180205190510.5499-1-paolo.valente@linaro.org> <20180205190510.5499-2-paolo.valente@linaro.org> <1517903761.9843.12.camel@gmx.de> Message-ID: <34a0aa9dead3a082615899b2830f60f1@natalenko.name> X-Sender: oleksandr@natalenko.name User-Agent: Roundcube Webmail/1.3.3 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=natalenko.name; s=arc-20170712; t=1517906273; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=DS1yzaNWEXIeXIAQMKBdmxokxpQy1g0dY2lYmXdTRBI=; b=ZEIToC7t91kRCSU+ZJLSf5DoxKvmg87GybjMM/vDWXQJ2wB1wlrQa56VrMONX85pY+hphU fVi/OVU9EAGRUMa2tD860mw+fqaT/5N6Qy9YxrXf2JoQR4Y+TAG7jHoyr6wQBdCDIAG7gb dsK2iHpIk3Dooex31axjigIh4xFCwLY= ARC-Seal: i=1; s=arc-20170712; d=natalenko.name; t=1517906273; a=rsa-sha256; cv=none; b=v71L+sHK1UtdVXsC+6aoAr7d7E5eF3i/62dD3IihRo8emyyvO8RgIdJ7PMH//6oCwqGVbpEY+a0W/3+uMBqfO6Cc3ITdXnqHelzbb0MSBO7Tz7gsxezDtPjndU6X8rNM/BV6vsQ4kkJvyU+uE2n84Aa9E1Ctby5hbvRFsD9C3ak= ARC-Authentication-Results: i=1; auth=pass smtp.auth=oleksandr@natalenko.name smtp.mailfrom=oleksandr@natalenko.name DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=natalenko.name; s=dkim-20170712; t=1517906273; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=DS1yzaNWEXIeXIAQMKBdmxokxpQy1g0dY2lYmXdTRBI=; b=JMyvtqXf5nod3KjeHhIkM8z1YinxMNHrLZdbTY+5caiU5esHRI9bbjkBVR2qjNlHlUbYKS MG7h9NUbHCFYbn2yfA6uPcNPHH3S9Ky3bkAJMxzuEIfmF2n/uBSZf1P2x6We4C8OzLYRg1 KVYQ15WDQs4vhTPivPFh9wJAZ0L4fiU= Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi. 06.02.2018 08:56, Mike Galbraith wrote: > I was doing kbuilds, and it blew up on me twice. Switching back to cfq > seemed to confirm it was indeed the patch causing trouble, but that's > by no means a certainty. Just to note, I was using v4.15.1, not the latest git HEAD. Are you able to reproduce it on the stable kernel? Also, assuming this issue might be unrelated to the BFQ itself, did you manage to reproduce the trouble with another blk-mq scheduler (not CFQ, but mq-deadline/Kyber)? Regards, Oleksandr