From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DD0ECA9EC7 for ; Tue, 5 Nov 2019 06:12:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1C8F720650 for ; Tue, 5 Nov 2019 06:12:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="FBtqOIpa" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387556AbfKEGMK (ORCPT ); Tue, 5 Nov 2019 01:12:10 -0500 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:32154 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2387488AbfKEGMK (ORCPT ); Tue, 5 Nov 2019 01:12:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1572934329; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jUKtXkiqnfc00yxvhNtkTvRjzLC+u/vAx+uKVNy5/cc=; b=FBtqOIpaZ2V9s2dTubyFN60BHWvVlSnGldOgvodCGCZo8usxX+sDK1HQZshpW05xo/0CKf glBdW1zik5v/MOh42qzPKFIUjxqPSeaETukBsmnRzMqBJysm0RZG/nhJl7LBe3XkqmfBOr J2ikeKawHLAAzVAyF8zE0xsT9ST0074= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-112-NkGVjf9BM7uNSfLEigRZtg-1; Tue, 05 Nov 2019 01:12:06 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 166EE107ACC2; Tue, 5 Nov 2019 06:12:04 +0000 (UTC) Received: from ming.t460p (ovpn-8-29.pek2.redhat.com [10.72.8.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CA7D65D6D0; Tue, 5 Nov 2019 06:11:54 +0000 (UTC) Date: Tue, 5 Nov 2019 14:11:50 +0800 From: Ming Lei To: Bart Van Assche Cc: kernel test robot , linux-scsi@vger.kernel.org, "Martin K . Petersen" , James Bottomley , Jens Axboe , "Ewan D . Milne" , Omar Sandoval , Christoph Hellwig , Kashyap Desai , Hannes Reinecke , Laurence Oberman , Bart Van Assche , lkp@lists.01.org Subject: Re: [scsi] 74eb6c22dc: suspend_stress.fail Message-ID: <20191105061150.GA17084@ming.t460p> References: <20191104085021.GF13369@xsang-OptiPlex-9020> <824c5a0b-a31a-b0a2-b14a-ab6edd294d07@acm.org> MIME-Version: 1.0 In-Reply-To: <824c5a0b-a31a-b0a2-b14a-ab6edd294d07@acm.org> User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: NkGVjf9BM7uNSfLEigRZtg-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: linux-scsi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-scsi@vger.kernel.org On Mon, Nov 04, 2019 at 07:52:59PM -0800, Bart Van Assche wrote: > On 2019-11-04 00:50, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): > >=20 > > commit: 74eb6c22dc70e395b333c9ca579855cd88db8845 ("[RFC PATCH V3 2/2] s= csi: core: don't limit per-LUN queue depth for SSD") > > url: https://github.com/0day-ci/linux/commits/Ming-Lei/scsi-core-avoid-= host-wide-host_busy-counter-for-scsi_mq/20191009-015827 > > base: https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git for-ne= xt > >=20 > > in testcase: suspend_stress > > with following parameters: > >=20 > > =09mode: freeze > > =09iterations: 10 >=20 > Hi Ming, >=20 > This is the second report by the build robot that this patch causes the > suspend_stress test to fail. I assume that that means that that test > failure is not a coincidence. The previous report (Oct-22) is available > at https://lore.kernel.org/linux-scsi/20191023003027.GD12647@shao2-debian= /. Yeah, it should be one real issue, and there are other issues too. I will w= ork out a new version for addressing all. Thanks, Ming