All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: kernel test robot <oliver.sang@intel.com>,
	linux-scsi@vger.kernel.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Jens Axboe <axboe@kernel.dk>,
	"Ewan D . Milne" <emilne@redhat.com>,
	Omar Sandoval <osandov@fb.com>, Christoph Hellwig <hch@lst.de>,
	Kashyap Desai <kashyap.desai@broadcom.com>,
	Hannes Reinecke <hare@suse.de>,
	Laurence Oberman <loberman@redhat.com>,
	Bart Van Assche <bart.vanassche@wdc.com>,
	lkp@lists.01.org
Subject: Re: [scsi] 74eb6c22dc: suspend_stress.fail
Date: Thu, 14 Nov 2019 09:25:32 +0800	[thread overview]
Message-ID: <20191114012532.GA14190@ming.t460p> (raw)
In-Reply-To: <cb814a0c-c636-e9f4-654a-3f21bd0db646@acm.org>

On Wed, Nov 13, 2019 at 09:00:29AM -0800, Bart Van Assche wrote:
> On 11/4/19 10:11 PM, Ming Lei wrote:
> > 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):
> > > > 
> > > > commit: 74eb6c22dc70e395b333c9ca579855cd88db8845 ("[RFC PATCH V3 2/2] scsi: 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-next
> > > > 
> > > > in testcase: suspend_stress
> > > > with following parameters:
> > > > 
> > > > 	mode: freeze
> > > > 	iterations: 10
> > > 
> > > Hi Ming,
> > > 
> > > 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 work
> > out a new version for addressing all.
> 
> Hi Ming,
> 
> Have you already made any progress? I'm asking because the v5.5 merge window
> is expected to open soon (this weekend).

Hi Bart,

I am busy on other things, and may not have time to look at this issue
for v5.5.

If you have idea for making the patch into mergeable, please go ahead.


thanks,
Ming


WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com>
To: lkp@lists.01.org
Subject: Re: [scsi] 74eb6c22dc: suspend_stress.fail
Date: Thu, 14 Nov 2019 09:25:32 +0800	[thread overview]
Message-ID: <20191114012532.GA14190@ming.t460p> (raw)
In-Reply-To: <cb814a0c-c636-e9f4-654a-3f21bd0db646@acm.org>

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

On Wed, Nov 13, 2019 at 09:00:29AM -0800, Bart Van Assche wrote:
> On 11/4/19 10:11 PM, Ming Lei wrote:
> > 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):
> > > > 
> > > > commit: 74eb6c22dc70e395b333c9ca579855cd88db8845 ("[RFC PATCH V3 2/2] scsi: 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-next
> > > > 
> > > > in testcase: suspend_stress
> > > > with following parameters:
> > > > 
> > > > 	mode: freeze
> > > > 	iterations: 10
> > > 
> > > Hi Ming,
> > > 
> > > 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(a)shao2-debian/.
> > 
> > Yeah, it should be one real issue, and there are other issues too. I will work
> > out a new version for addressing all.
> 
> Hi Ming,
> 
> Have you already made any progress? I'm asking because the v5.5 merge window
> is expected to open soon (this weekend).

Hi Bart,

I am busy on other things, and may not have time to look at this issue
for v5.5.

If you have idea for making the patch into mergeable, please go ahead.


thanks,
Ming

  reply	other threads:[~2019-11-14  1:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 10:09 [PATCH V3 0/2] scsi: avoid atomic operations in IO path Ming Lei
2019-10-08 10:09 ` [PATCH V3 1/2] scsi: core: avoid host-wide host_busy counter for scsi_mq Ming Lei
2019-10-08 10:09 ` [RFC PATCH V3 2/2] scsi: core: don't limit per-LUN queue depth for SSD Ming Lei
2019-10-08 19:33   ` kbuild test robot
2019-10-09  8:29   ` Dan Carpenter
2019-10-09  8:29     ` Dan Carpenter
2019-11-04  8:50   ` [scsi] 74eb6c22dc: suspend_stress.fail kernel test robot
2019-11-04  8:50     ` kernel test robot
2019-11-05  3:52     ` Bart Van Assche
2019-11-05  3:52       ` Bart Van Assche
2019-11-05  6:11       ` Ming Lei
2019-11-05  6:11         ` Ming Lei
2019-11-13 17:00         ` Bart Van Assche
2019-11-13 17:00           ` Bart Van Assche
2019-11-14  1:25           ` Ming Lei [this message]
2019-11-14  1:25             ` Ming Lei
2019-11-16  8:54     ` Ming Lei
2019-11-16  8:54       ` Ming Lei
2019-11-21  6:50       ` Oliver Sang
2019-11-21  6:50         ` Oliver Sang
2019-11-21  7:36         ` Ming Lei
2019-11-21  7:36           ` Ming Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191114012532.GA14190@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=axboe@kernel.dk \
    --cc=bart.vanassche@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=loberman@redhat.com \
    --cc=martin.petersen@oracle.com \
    --cc=oliver.sang@intel.com \
    --cc=osandov@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.