linux-kernel - RE: [PATCH v2] scsi: ufs: critical health condition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <DM6PR04MB6575482D4C10F31D633E95F3FCF72@DM6PR04MB6575.namprd04.prod.outlook.com>
Date: Wed, 5 Feb 2025 18:04:22 +0000
From: Avri Altman <Avri.Altman@....com>
To: Bart Van Assche <bvanassche@....org>, "Martin K . Petersen"
	<martin.petersen@...cle.com>
CC: "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2] scsi: ufs: critical health condition

> 
> On 2/4/25 6:31 AM, Avri Altman wrote:
> > +static ssize_t critical_health_show(struct device *dev,
> > +                                 struct device_attribute *attr, char
> > +*buf) {
> > +     struct ufs_hba *hba = dev_get_drvdata(dev);
> > +
> > +     return sysfs_emit(buf, "%d\n", hba->dev_info.critical_health); }
> 
> Hi Avri,
> 
> My understanding is that the UFS 4.1 standard supports reporting a critical
> health event repeatedly while this patch does not allow users to figure out
> whether a critical event has been reported once or repeatedly. Has it been
> considered to report the number of times a critical health event has been
> reported by a UFS device instead of only one bit of information?
I was told it would report only once.
Let me check again and get back to you on that.

Thanks,
Avri

> 
> Thanks,
> 
> Bart.