public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Bart Van Assche <bvanassche@acm.org>
Cc: Santosh Yaraganavi <santoshsy@gmail.com>,
	Can Guo <cang@codeaurora.org>, Bean Huo <beanhuo@micron.com>,
	Vishak G <vishak.g@samsung.com>,
	Stanley Chu <stanley.chu@mediatek.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Girish K S <girish.shivananjappa@linaro.org>,
	linux-scsi@vger.kernel.org, Asutosh Das <asutoshd@codeaurora.org>,
	Vinayak Holikatti <vinholikatti@gmail.com>
Subject: Re: [PATCH] scsi: ufs: Improve SCSI abort handling
Date: Tue, 14 Dec 2021 11:35:43 -0500	[thread overview]
Message-ID: <5a5cd1dde61e656e15df3767e1a6d2cc362d280d.camel@HansenPartnership.com> (raw)
In-Reply-To: <163729506335.21244.1193812894951616835.b4-ty@oracle.com>

On Thu, 2021-11-18 at 23:16 -0500, Martin K. Petersen wrote:
> On Thu, 4 Nov 2021 11:10:53 -0700, Bart Van Assche wrote:
> 
> > The following has been observed on a test setup:
> > 
> > WARNING: CPU: 4 PID: 250 at drivers/scsi/ufs/ufshcd.c:2737
> > ufshcd_queuecommand+0x468/0x65c
> > Call trace:
> >  ufshcd_queuecommand+0x468/0x65c
> >  scsi_send_eh_cmnd+0x224/0x6a0
> >  scsi_eh_test_devices+0x248/0x418
> >  scsi_eh_ready_devs+0xc34/0xe58
> >  scsi_error_handler+0x204/0x80c
> >  kthread+0x150/0x1b4
> >  ret_from_fork+0x10/0x30
> > 
> > [...]
> 
> Applied to 5.16/scsi-fixes, thanks!
> 
> [1/1] scsi: ufs: Improve SCSI abort handling
>       https://git.kernel.org/mkp/scsi/c/3ff1f6b6ba6f

OK, so now we have a conflict between fixes and queue.  My impression
is that the patch causing the conflict:

https://lore.kernel.org/all/20211203231950.193369-14-bvanassche@acm.org/

Actually supersedes this one, so I can simply drop the entirety of this
patch in fixes, is that correct?

James



  reply	other threads:[~2021-12-14 16:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20211104181111epcas2p2965ba25c905be783c39f098210cc4c61@epcms2p2>
2021-11-04 18:10 ` [PATCH] scsi: ufs: Improve SCSI abort handling Bart Van Assche
2021-11-04 22:20   ` Bean Huo
2021-11-04 22:39   ` Daejun Park
2021-11-04 23:14     ` Bart Van Assche
2021-11-04 23:39       ` Daejun Park
2021-11-04 23:54         ` Bart Van Assche
2021-11-05  1:53           ` Daejun Park
2021-11-07  6:59   ` Stanley Chu
2021-11-09  4:03   ` Martin K. Petersen
2021-11-19  4:16   ` Martin K. Petersen
2021-12-14 16:35     ` James Bottomley [this message]
2021-12-14 17:37       ` Bart Van Assche
2021-12-14 17:43         ` James Bottomley
2021-12-14 17:45           ` Bart Van Assche

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=5a5cd1dde61e656e15df3767e1a6d2cc362d280d.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=adrian.hunter@intel.com \
    --cc=asutoshd@codeaurora.org \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=girish.shivananjappa@linaro.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=santoshsy@gmail.com \
    --cc=stanley.chu@mediatek.com \
    --cc=vinholikatti@gmail.com \
    --cc=vishak.g@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox