Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Christian Kühnke" <christian@kuehnke.de>
Cc: stable@vger.kernel.org, dlemoal@kernel.org
Subject: Re: Request inclusion of 18676c6aab0863618eb35443e7b8615eea3535a9 into stable 6.6
Date: Wed, 29 Jan 2025 10:06:58 +0100	[thread overview]
Message-ID: <2025012949-agnostic-padlock-e746@gregkh> (raw)
In-Reply-To: <64f08e31-dff8-4e86-ac5a-95ddc756031e@kuehnke.de>

On Wed, Jan 29, 2025 at 09:39:42AM +0100, Christian Kühnke wrote:
> Hi all,
> 
> I have been sent here from the linux-ide mailing list. Over there, I have
> reported an issue with the 6.6 stable series of the kernel, starting with
> 6.6.51. The root cause is as follows:
> 
> On 12.09.2024, commit 872f86e1757bbb0a334ee739b824e47c448f5ebc ("ata:
> libata-scsi: Check ATA_QCFLAG_RTF_FILLED before using result_tf") was
> applied to 6.6, adding checks of ATA_QCFLAG_RTF_FILLED to libata_scsi. The
> patch seen in baseline commit 18676c6aab0863618eb35443e7b8615eea3535a9
> ("ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf()") should
> have gone together with this.
> 
> Without it, I receive errors retrieving SMART data from SATA disks via a
> C602 SAS controller, apparently because in this situation
> ATA_QCFLAG_RTF_FILLED is not set.
> 
> I applied 18676c6aab0863618eb35443e7b8615eea3535a9 from baseline to 6.6.74
> and the problem went away.
> 
> If you need any further information, do not hesitate to contact me (linux
> user since 0.99.x, but only debugging it once every few years or so...).
> 

Now queued up, thanks.

greg k-h

      reply	other threads:[~2025-01-29  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  8:39 Request inclusion of 18676c6aab0863618eb35443e7b8615eea3535a9 into stable 6.6 Christian Kühnke
2025-01-29  9:06 ` Greg KH [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=2025012949-agnostic-padlock-e746@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christian@kuehnke.de \
    --cc=dlemoal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox