Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>,
	"Martin K . Petersen" <mkp@kernel.org>,
	John Garry <john.garry@linux.dev>, Hannes Reinecke <hare@suse.de>,
	Jens Axboe <axboe@kernel.dk>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Justinien Bouron <jbouron@amazon.com>
Cc: Gunnar Kudrjavets <gunnarku@amazon.com>, stable@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Add max sector quirk to INTEL SSDSCKKB240G8
Date: Tue, 17 Nov 2026 13:55:19 +0100	[thread overview]
Message-ID: <avxOtx5ueJXmYMlz@ryzen> (raw)
In-Reply-To: <179491952051.3464613.10156120067978467700.b4-ty@kernel.org>

On Tue, Nov 17, 2026 at 01:45:20PM +0100, Niklas Cassel wrote:
> On Mon, 16 Nov 2026 12:54:30 -0800, Justinien Bouron wrote:
> > INTEL SSDSCKKB240G8 with firmware version XC311102 runs into FPDMA
> > timeout errors when queue/max_sectors_kb is set to
> > BLK_DEF_MAX_SECTORS_CAP = 4096KiB / 8192 sectors. Similar to model
> > SSDSC2KG480G8, the issue disappears when setting this max size to 8191
> > sectors, thus apply the same quirk.
> > 
> > Firmware version X5A1ME59 for SSDSCKKB240G8 is un-affected by this bug
> > thus keep the quirk specific to firmware XC311102.
> > 
> > [...]
> 
> Applied to libata/linux.git (for-7.5), thanks!
> 
> [1/1] ata: libata-core: Add max sector quirk to INTEL SSDSCKKB240G8
>       https://git.kernel.org/libata/linux/c/3dccf22a
> 

I moved this to for-7.4-fixes instead, because of the severity of the bug
and that it is quite recent.


Kind regards,
Niklas

      reply	other threads:[~2026-11-17 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 20:54 [PATCH] ata: libata-core: Add max sector quirk to INTEL SSDSCKKB240G8 Justinien Bouron
2026-11-16 21:39 ` Damien Le Moal
2026-11-17 12:45 ` Niklas Cassel
2026-11-17 12:55   ` Niklas Cassel [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=avxOtx5ueJXmYMlz@ryzen \
    --to=cassel@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=gunnarku@amazon.com \
    --cc=hare@suse.de \
    --cc=jbouron@amazon.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=john.garry@linux.dev \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkp@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