public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Martin Kepplinger <martin.kepplinger@puri.sm>
Cc: Bart Van Assche <bvanassche@acm.org>,
	Can Guo <cang@codeaurora.org>,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
	kernel@puri.sm
Subject: Re: [PATCH] block: Fix bug in runtime-resume handling
Date: Mon, 24 Aug 2020 16:13:43 -0400	[thread overview]
Message-ID: <20200824201343.GA344424@rowland.harvard.edu> (raw)
In-Reply-To: <3e5a465e-8fe0-b379-a80e-23e2f588c71a@acm.org>

On Mon, Aug 24, 2020 at 10:48:32AM -0700, Bart Van Assche wrote:
> On 2020-08-23 07:57, Alan Stern wrote:
> > The problem is fixed by checking that the queue's runtime-PM status
> > isn't RPM_SUSPENDED before allowing a request to be issued, [ ... ]
> 
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
> 
> Can, can you help with testing this patch?
> 
> Thanks,
> 
> Bart.

Martin:

(I forgot to ask this question several weeks ago, while you were running 
your tests.  Better ask it now before I forget again...)

I suspect the old runtime-PM code in the block layer would have worked 
okay in your SD cardreader test if the BLK_MQ_REQ_PREEMPT flag had not 
been set.  Do you know why the flag was set, or what line of code caused 
it to be set?

As I recall, the request that failed was a read-ahead.  It's not clear 
to me why such a request would need to have BLK_MQ_REQ_PREEMPT set.  
Although there may be other reasons for having that flag, at this point 
we're concerned with requests that are part of the runtime-resume 
procedure.  A read-ahead does not fall into that category.

Do you think you can find the answer?  Perhaps we should add a separate 
BLK_MQ_REQ_PM flag.

Alan Stern

  reply	other threads:[~2020-08-24 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9b80ca7c-39f8-e52d-2535-8b0baf93c7d1@puri.sm>
     [not found] ` <425990b3-4b0b-4dcf-24dc-4e7e60d5869d@puri.sm>
     [not found]   ` <20200807143002.GE226516@rowland.harvard.edu>
     [not found]     ` <b0abab28-880e-4b88-eb3c-9ffd927d1ed9@puri.sm>
     [not found]       ` <20200808150542.GB256751@rowland.harvard.edu>
     [not found]         ` <d3b6f7b8-5345-1ae1-4f79-5dde226e74f1@puri.sm>
     [not found]           ` <20200809152643.GA277165@rowland.harvard.edu>
     [not found]             ` <60150284-be13-d373-5448-651b72a7c4c9@puri.sm>
     [not found]               ` <20200810141343.GA299045@rowland.harvard.edu>
     [not found]                 ` <6f0c530f-4309-ab1e-393b-83bf8367f59e@puri.sm>
2020-08-23 14:57                   ` [PATCH] block: Fix bug in runtime-resume handling Alan Stern
2020-08-24 17:48                     ` Bart Van Assche
2020-08-24 20:13                       ` Alan Stern [this message]
2020-08-26  7:48                         ` Martin Kepplinger
2020-08-27 17:42                           ` Martin Kepplinger
2020-08-27 20:29                             ` Alan Stern
2020-08-29  7:24                               ` Martin Kepplinger
2020-08-29 15:26                                 ` Alan Stern
2020-08-29 16:33                                   ` Martin Kepplinger
2020-08-29 18:56                                     ` Alan Stern
2020-08-30  0:38                                       ` Bart Van Assche
2020-08-30  1:06                                         ` Alan Stern

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=20200824201343.GA344424@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=kernel@puri.sm \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.kepplinger@puri.sm \
    /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