linux-kernel - Re: [PATCH] scsi: Add SCSI error events, sent as kobject uevents by mid-layer

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: <CAPE3x16MrkQXFasVaaHBxhH2QvQ4H5cDiE3ae=-nYjuEKV-NBw@mail.gmail.com>
Date: Thu, 15 May 2025 13:03:22 -0700
From: Salomon Dushimirimana <salomondush@...gle.com>
To: James Bottomley <James.Bottomley@...senpartnership.com>
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>, linux-scsi@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scsi: Add SCSI error events, sent as kobject uevents by mid-layer

Hi,

I agree with the recommended use of ftrace or blktrace for tracing.
However, our primary goal for using uevents was not merely for
collecting trace information. We are using uevents as a notification
mechanism for userspace workflows to determine repair workflows (swap
/ remove a failing device).

We are open to any feedback on other notification recommendations for
such use cases.




Salomon Dushimirimana

On Tue, May 13, 2025 at 1:27 PM James Bottomley
<James.Bottomley@...senpartnership.com> wrote:
>
> On Tue, 2025-05-13 at 12:00 -0700, Salomon Dushimirimana wrote:
> > Hi James and Martin
> >
> > I wanted to follow up on this patch! It's a decently sized patch, so
> > it might take some time, but I'd love to hear your thoughts and
> > address any feedback!!
>
> I think the first fundamental question should be why is this a uevent?
> It looks like what you're obtaining is really tracing information on
> the retry and we could simply add it as another tracepoint in the
> existing blktrace infrastructure SCSI already has.
>
> Regards,
>
> James
>