All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: stable@vger.kernel.org, yibin.ding@unisoc.com, ulf.hansson@linaro.org
Subject: Re: [PATCH 4.19] mmc: block: Fix in_flight[issue_type] value error
Date: Sun, 27 Aug 2023 10:54:56 +0200	[thread overview]
Message-ID: <2023082745-commodore-subdued-84a8@gregkh> (raw)
In-Reply-To: <9aa71735-a941-dc24-e04b-529d6092e340@intel.com>

On Wed, Aug 23, 2023 at 08:12:32PM +0300, Adrian Hunter wrote:
> From: Yibin Ding <yibin.ding@unisoc.com>
> 
> commit 4b430d4ac99750ee2ae2f893f1055c7af1ec3dc5 upstream.
> 
> For a completed request, after the mmc_blk_mq_complete_rq(mq, req)
> function is executed, the bitmap_tags corresponding to the
> request will be cleared, that is, the request will be regarded as
> idle. If the request is acquired by a different type of process at
> this time, the issue_type of the request may change. It further
> caused the value of mq->in_flight[issue_type] to be abnormal,
> and a large number of requests could not be sent.
> 
> p1:					      p2:
> mmc_blk_mq_complete_rq
>   blk_mq_free_request
> 					      blk_mq_get_request
> 					        blk_mq_rq_ctx_init
> mmc_blk_mq_dec_in_flight
>   mmc_issue_type(mq, req)
> 
> This strategy can ensure the consistency of issue_type
> before and after executing mmc_blk_mq_complete_rq.
> 
> Fixes: 81196976ed94 ("mmc: block: Add blk-mq support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yibin Ding <yibin.ding@unisoc.com>
> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> Link: https://lore.kernel.org/r/20230802023023.1318134-1-yunlong.xing@unisoc.com
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> (cherry picked from commit 4b430d4ac99750ee2ae2f893f1055c7af1ec3dc5)
> (backport to 4.19.y)
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
>  drivers/mmc/core/block.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-08-27  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 11:29 FAILED: patch "[PATCH] mmc: block: Fix in_flight[issue_type] value error" failed to apply to 4.19-stable tree gregkh
2023-08-23 17:12 ` [PATCH 4.19] mmc: block: Fix in_flight[issue_type] value error Adrian Hunter
2023-08-27  8:54   ` Greg KH [this message]

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=2023082745-commodore-subdued-84a8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=adrian.hunter@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=yibin.ding@unisoc.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.