From: Salvatore Bonaccorso <carnil@debian.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Christian Heusel <christian@heusel.eu>,
Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
Igor Pylypiv <ipylypiv@google.com>,
linux-ide@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED][STABLE] hdparm errors since 28ab9769117c
Date: Mon, 19 Aug 2024 20:45:56 +0200 [thread overview]
Message-ID: <ZsOS5DmRnS3ab_9W@eldamar.lan> (raw)
In-Reply-To: <d224b165-14dd-4131-b923-1ef5bdf3fb7f@leemhuis.info>
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@web.de/
> 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@web.de/
> #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
prev parent reply other threads:[~2024-08-19 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 17:23 [REGRESSION][BISECTED][STABLE] hdparm errors since 28ab9769117c Christian Heusel
2024-08-07 18:26 ` Damien Le Moal
2024-08-07 22:10 ` Niklas Cassel
2024-08-09 14:30 ` Niklas Cassel
2024-08-09 15:21 ` Damien Le Moal
2024-08-09 15:34 ` Damien Le Moal
2024-08-09 18:42 ` Christian Heusel
2024-08-09 20:13 ` Christian Heusel
2024-08-12 9:26 ` Linux regression tracking (Thorsten Leemhuis)
2024-08-19 18:45 ` Salvatore Bonaccorso [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=ZsOS5DmRnS3ab_9W@eldamar.lan \
--to=carnil@debian.org \
--cc=cassel@kernel.org \
--cc=christian@heusel.eu \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=ipylypiv@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.