mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <Avri.Altman@wdc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scsi: ufs: critical health condition
Date: Thu, 6 Feb 2025 07:54:21 -0800	[thread overview]
Message-ID: <b962df63-42c4-4bc9-9815-9871be1ce2d5@acm.org> (raw)
In-Reply-To: <DM6PR04MB65757320A1761FE473BFC5CCFCF62@DM6PR04MB6575.namprd04.prod.outlook.com>

On 2/6/25 12:54 AM, Avri Altman wrote:
> After some further internal discussions: The set conditions are
> vendor specific; The device may set it as many times it wants
> depending on its criticality. The spec does not define that nor what
> the host should do. So there is this concern that some vendors will
> report multiple times, while other wont. Hence, reading
> critical_health = 1 might be misleading. What do you think?

How about emitting a uevent if a critical health condition has been
reported by a UFS device? See also sdev_evt_send().

Thanks,

Bart.


  reply	other threads:[~2025-02-06 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 14:31 Avri Altman
2025-02-05 18:00 ` Bart Van Assche
2025-02-05 18:04   ` Avri Altman
2025-02-05 19:07   ` Avri Altman
2025-02-06  8:54     ` Avri Altman
2025-02-06 15:54       ` Bart Van Assche [this message]
2025-02-06 17:47         ` Avri Altman
2025-02-06 18:08           ` Bart Van Assche
2025-02-06 18:25             ` Avri Altman

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=b962df63-42c4-4bc9-9815-9871be1ce2d5@acm.org \
    --to=bvanassche@acm.org \
    --cc=Avri.Altman@wdc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®