Re: [REGRESSION][BISECTED][STABLE] hdparm errors since 28ab9769117c

From: Salvatore Bonaccorso
Date: Mon Aug 19 2024 - 14:46:34 EST


Hi,

On Mon, Aug 12, 2024 at 11:26:53AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 09.08.24 22:13, Christian Heusel wrote:
> > On 24/08/09 08:42PM, Christian Heusel wrote:
> >> On 24/08/09 08:34AM, Damien Le Moal wrote:
> >>> On 2024/08/07 15:10, Niklas Cassel wrote:
> >>>> On Wed, Aug 07, 2024 at 11:26:46AM -0700, Damien Le Moal wrote:
> >>>>> On 2024/08/07 10:23, Christian Heusel wrote:
> >>>>>>
> >>>>>> on my NAS I am encountering the following issue since v6.6.44 (LTS),
> >>>>>> when executing the hdparm command for my WD-WCC7K4NLX884 drives to get
> >>>>>> the active or standby state:
> >>> [...]
> >>> Yes, indeed. I do not want to revert any of these recent patches, because as you
> >>> rightly summarize here, these fix something that has been broken for a long
> >>> time. We were just lucky that we did not see more application failures until
> >>> now, or rather unlucky that we did not as that would have revealed these
> >>> problems earlier.
> >>
> >> It seems like this does not only break hdparm but also hddtemp, which
> >> does not use hdparm as dep as far as I can tell:
> >
> > As someone on the same thread has pointed out, this also seems to affect
> > udiskd:
> >
> > https://github.com/storaged-project/udisks/issues/732
>
> For the record, three more people reported similar symptoms in the past
> few days:
>
> https://lore.kernel.org/all/e620f887-a674-f007-c17b-dc16f9a0a588@xxxxxx/
> https://bugzilla.kernel.org/show_bug.cgi?id=219144
>
> Ciao, Thorsten
>
> P.S.: I for the tracking for now assume those are indeed the same problem:
>
> #regzbot dup:
> https://lore.kernel.org/all/e620f887-a674-f007-c17b-dc16f9a0a588@xxxxxx/
> #regzbot dup: https://bugzilla.kernel.org/show_bug.cgi?id=219144

AFAICS, this has now been reverted upstream with fa0db8e56878 ("Revert
"ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error"")
in 6.11-rc4 and the revert was as well backported to stable releases
(5.15.165, 6.1.106, 6.6.47 and 6.10.6)

Regards,
Salvatore