cklists#DnsBlocklists-dnsbl-block
                              for more information.
                             [172.105.105.114 listed in list.dnswl.org]
 -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
 -0.1 DKIM_VALID_EF          Message has a valid DKIM or DK signature from
                             envelope-from domain
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                             valid
 -0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from
                             author's domain
 -1.0 MAILING_LIST_MULTI     Multiple indicators imply a widely-seen list
                             manager
 -0.0 DKIMWL_WL_HIGH         DKIMwl.org - High trust sender
SpamTally: Final spam score: -11

Hello Salvatore,

On Wed, Jan 14, 2026 at 12:47:45PM +0100, Salvatore Bonaccorso wrote:
> A user reported a regression affecting his devices after 9b8b84879d4a
> ("block: Increase BLK_DEF_MAX_SECTORS_CAP") which maybe needs a
> similar quirk like 2e9832713631 ("ata: libata-core: Quirk DELLBOSS VD
> max_sectors").

The drive:
> Dec 10 18:56:03 kernel: ata1.00: Model 'INTEL SSDSC2KG480G8', rev 'XCV10120', applying quirks: zeroaftertrim
> Dec 10 18:56:03 kernel: ata1.00: ATA-10: INTEL SSDSC2KG480G8, XCV10120, max UDMA/133

The SATA controller:
00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller [8086:a353] (rev 10) (prog-if 01 [AHCI 1.0])
	DeviceName: Onboard - SATA
	Subsystem: Dell Device [1028:0924]


Perhaps the user could run:
https://github.com/floatious/max-sectors-quirk/blob/master/find-max-sectors.sh

So we could find which max sectors value we should quirk the device with,
since while the drive obviously chokes on a command of size 4 MiB / 8192
sectors, it might be able to handle something larger than 1280 KiB / 2560
sectors.


Kind regard,
Niklas


From - Wed Jan 14 14:32:16 2026
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <io-uring+bounces-11702-hi=josie.lol@vger.kernel.org>
Delivered-To: hi@josie.lol
Received: from witcher.mxrouting.net
	by witcher.mxrouting.net with LMTP
	id KBXwCeyoZ2nzyDAAYBR5ng
	(envelope-from <io-uring+bounces-11702-hi=josie.lol@vger.kernel.org>)
	for <hi@josie.lol>; Wed, 14 Jan 2026 14:32:12 +0000
Return-path: <io-uring+bounces-11702-hi=josie.lol@vger.kernel.org>
Envelope-to: hi@josie.lol
Delivery-date: Wed, 14 Jan 2026 14:32:12 +0000
Received: from sto.lore.kernel.org ([172.232.135.74])
	by witcher.mxrouting.net with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.98)
	(envelope-from <io-uring+bounces-11702-hi=josie.lol@vger.kernel.org>)
	id 1vg1ut-0000000Di4F-3Kvi
	for hi@josie.lol;
	Wed, 14 Jan 2026 14:32:12 +0000
Received: from smtp.subspace.kernel.org (conduit.subspace.kernel.org [100.90.174.1])
	by sto.lore.kernel.org (Postfix) with ESMTP id 1DA2B3016664
	for <hi@josie.lol>; Wed, 14 Jan 2026 14:30:22 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.subspace.kernel.org (Postfix) with ESMTP id A47482D94BB;
	Wed, 14 Jan 2026 14:30:11 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="jg5xEf4N"
X-Original-To: io-uring@vger.kernel.org
Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 072732F0C74
	for <io-uring@vger.kernel.org>; Wed, 14 Jan 2026 14:30:09 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.53
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1768401011; cv=none; b=IcUi1ULjZCTASQQJj3+KarUxwHSwf49xM9ID64FVxngrYmesON+Pm55F/j4xez9IJ3+vZF0GgcMHGO3trV6/B1DGegciw9+Z0Jb6mOfvUBko8OEEQg8pEztDSu5ZFuCP3Zj4IAr5XS6y/5ulkIcP9LNpnB/5RFN29Kx8p/WHbmk=
ARC-Message-Signature:i=1