Received: from mail-pl1-f182.google.com (mail-pl1-f182.google.com [209.85.214.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C979B14AA6 for ; Thu, 17 Aug 2023 17:20:20 +0000 (UTC) Received: by mail-pl1-f182.google.com with SMTP id d9443c01a7336-1bdf1abee23so67335ad.0 for ; Thu, 17 Aug 2023 10:20:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20221208.gappssmtp.com; s=20221208; t=1692292820; x=1692897620; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=MEEMLBU7KyGRl1jyNCYxrTksFBbZzFyIftfWwVnH+fI=; b=PxIUkR6QCMelRphwb7nNTBBi5xX67tY9gBxIJQneBYD/lufdGIcKBXtI0wXLmhh6yK IXKYehGZRpVB06BRWgNaJIme2xyrwWLBp8fwJuXiNGYjgAn2iHxtCvTrrTfFyWf6LoHg cNGAJONtBhpceK1CP9h5IuHNaITDgJwoDPGF8hteE3T1gES4G64Z1GvqI2734PqBvGt9 ycTCi8iTcAvOjfj04kWI6NI7+e6IzqZHU7ZAmvi1vt5e8wul5LM9nvWZDT/wnXM4a0/2 880w8DBgAwaBq0ukUfdyvtlD3oFooVcxMmIUemt+6E+Kz23Sm4Yai9k+3i1k7NrF036w OP8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692292820; x=1692897620; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MEEMLBU7KyGRl1jyNCYxrTksFBbZzFyIftfWwVnH+fI=; b=bcVlfzKOZtuoY9ltTvNdLDMvHTEmMkcXbCwK8EfNIdIsC8wKSxA7Hw119EB30t9LA6 SE0FfG/Gx4ZN3IjZGndQiVIwQtJJ0ptJFMEtHgNqzz9JP44ysyKqDy4e6lxV0HPXLPVf SaO9ZRaXs1N9o1YUWixqdZBMg3eoo48WPKEUEELBFh9qluZpwuh4CB8OmpFs/0vs23ha DRl3yAblO93fCdExLV3Z7uQq4qb6FbtLOeXM5d/S1urU7o4mG/lylt9RjV7Qj51gDcNB qilY5/QAGYcXAxXvWpNefoDGEmf9EE5ehFQhl2+7WdOU3Ty4UE2c9nrjjcbSlF8YTCEn tv1Q== X-Gm-Message-State: AOJu0Yw8v8++Uo0ORH6FTAyBJPzWRP67aubXx5KYNvUjM65gk5oKxIdj VS0PORfjA94D0+Mph0aJgYlFRQ== X-Google-Smtp-Source: AGHT+IHoZ5NKn64ndpHfUzrusz+K6F4l2vMaKDWesViwP5pjrPID8odhdTPKfLUHX0peIYDLzKhc3w== X-Received: by 2002:a17:903:248:b0:1b8:9215:9163 with SMTP id j8-20020a170903024800b001b892159163mr6305223plh.6.1692292820095; Thu, 17 Aug 2023 10:20:20 -0700 (PDT) Received: from [192.168.1.136] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id q10-20020a170902daca00b001bc2831e1a9sm24212plx.90.2023.08.17.10.20.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 17 Aug 2023 10:20:19 -0700 (PDT) Message-ID: <8c262b00-9856-49fa-b425-da863efdff7d@kernel.dk> Date: Thu, 17 Aug 2023 11:20:17 -0600 Precedence: bulk X-Mailing-List: oe-lkp@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2] blk-mq: release scheduler resource when request complete Content-Language: en-US To: Chengming Zhou , Bart Van Assche , hch@lst.de Cc: oe-lkp@lists.linux.dev, lkp@intel.com, Chuck Lever , linux-block@vger.kernel.org, cel@kernel.org, linux-kernel@vger.kernel.org, kernel test robot References: <202308172100.8ce4b853-oliver.sang@intel.com> <317715dc-f6e4-1847-5b78-b2d8184b446a@linux.dev> From: Jens Axboe In-Reply-To: <317715dc-f6e4-1847-5b78-b2d8184b446a@linux.dev> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 8/17/23 9:29 AM, Chengming Zhou wrote: > On 2023/8/17 22:50, Bart Van Assche wrote: >> On 8/17/23 07:41, kernel test robot wrote: >>> [ 222.622837][ T2216] statistics for priority 1: i 276 m 0 d 276 c 278 >>> [ 222.629307][ T2216] WARNING: CPU: 0 PID: 2216 at block/mq-deadline.c:680 dd_exit_sched (block/mq-deadline.c:680 (discriminator 3)) >> >> The above information shows that dd_inserted_request() has been called >> 276 times and also that dd_finish_request() has been called 278 times. > > Thanks much for your help. > > This patch indeed introduced a regression, postflush requests will be completed > twice, so here dd_finish_request() is more than dd_inserted_request(). > > diff --git a/block/blk-mq.c b/block/blk-mq.c > index a8c63bef8ff1..7cd47ffc04ce 100644 > --- a/block/blk-mq.c > +++ b/block/blk-mq.c > @@ -686,8 +686,10 @@ static void blk_mq_finish_request(struct request *rq) > { > struct request_queue *q = rq->q; > > - if (rq->rq_flags & RQF_USE_SCHED) > + if (rq->rq_flags & RQF_USE_SCHED) { > q->elevator->type->ops.finish_request(rq); > + rq->rq_flags &= ~RQF_USE_SCHED; > + } > } > > > Clear RQF_USE_SCHED flag here should fix this problem, which should be ok > since finish_request() is the last callback, this flag isn't needed anymore. > > Jens, should I send this diff as another patch or resend updated v3? I don't think this is the right solution, it makes all kinds of assumptions on what that flag is and when it's safe to clear it. It's a very fragile fix, I think we need to do better than that. -- Jens Axboe