public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Alexey Klimov" <alexey.klimov@linaro•org>
To: "Bart Van Assche" <bvanassche@acm•org>,
	<linux-scsi@vger•kernel.org>, <mani@kernel•org>,
	<linux-arm-msm@vger•kernel.org>
Cc: <alim.akhtar@samsung•com>, <avri.altman@wdc•com>,
	<linux-next@vger•kernel.org>, <linux-kernel@vger•kernel.org>
Subject: Re: [linux-next] potential deadlock in ufshcd?
Date: Sun, 07 Dec 2025 23:15:51 +0000	[thread overview]
Message-ID: <DESD81PA9NI9.NKA6IOV0ROX9@linaro.org> (raw)
In-Reply-To: <46cf2cb9-76f4-4d73-be3d-88fcbe7055f4@acm.org>

On Sun Dec 7, 2025 at 3:18 PM GMT, Bart Van Assche wrote:
> On 12/6/25 7:07 PM, Alexey Klimov wrote:
>> Is it a known problem? I can test potential changes to resolve this
>> or try to collect more debug data if needed.
>
> Please help with testing these two kernel patches:
> * "[PATCH] ufs: core: Fix a deadlock in the frequency scaling code"
> (https://lore.kernel.org/linux-scsi/20251204181548.1006696-1-bvanassche@acm.org/).

Thanks! This looks like that one about fixing deadlock does
the job. I provided tested-by tag there.

> * "[PATCH] ufs: core: Fix an error handler crash"
> (https://lore.kernel.org/linux-scsi/20251204170457.994851-1-bvanassche@acm.org/).

I didn't test this one yet though.

Best regards,
Alexey

      reply	other threads:[~2025-12-07 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07  5:07 [linux-next] potential deadlock in ufshcd? Alexey Klimov
2025-12-07 15:18 ` Bart Van Assche
2025-12-07 23:15   ` Alexey Klimov [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=DESD81PA9NI9.NKA6IOV0ROX9@linaro.org \
    --to=alexey.klimov@linaro$(echo .)org \
    --cc=alim.akhtar@samsung$(echo .)com \
    --cc=avri.altman@wdc$(echo .)com \
    --cc=bvanassche@acm$(echo .)org \
    --cc=linux-arm-msm@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-scsi@vger$(echo .)kernel.org \
    --cc=mani@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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