public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
	Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Ondrej Kozina <okozina@redhat.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Alan Adamson <alan.adamson@oracle.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] block: cleanup and fix batch completion adding conditions
Date: Wed, 19 Mar 2025 19:54:43 +0100	[thread overview]
Message-ID: <38b3eb9b-6448-4684-9f47-f4b64e5415cd@gmail.com> (raw)
In-Reply-To: <625382fc-8503-4e19-b571-6245fb4d1317@kernel.dk>

On 3/11/25 4:00 PM, Jens Axboe wrote:
> On 3/11/25 8:59 AM, Milan Broz wrote:
>> On 3/11/25 4:03 AM, Shinichiro Kawasaki wrote:
>>>
>>> I created fix candidate patches to address the blktests nvme/039 failure [1].
>>> This may work for the failures Ondrej and Milan observe too, hopefully.
>>
>> Hi,
>>
>> I quickly tried to run the test with todays' mainline git and mentioned two patches:
>>    https://lkml.kernel.org/linux-block/20250311024144.1762333-2-shinichiro.kawasaki@wdc.com/
>>    https://lkml.kernel.org/linux-block/20250311024144.1762333-3-shinichiro.kawasaki@wdc.com/
>> and it looks like our SED Opal tests are fixed, no errors or warnings, thanks!
>>
>>> Jens, Alan, could you take a look in the patches and see if they make sense?
>>
>> Please, fix it before the 6.14 final, this could cause serious data corruption, at least
>> on systems using SED Opal drives.
> 
> Fix is already queued up.

Hi Jens,

it seems the bug was "successfully" backported to stable 6.13.4+ and I do not see any fix
in the stable queue yet.

We were hit by it today, as all locked ranges for Opal devices now returning empty data
instead of failing read.

Please could you check what need to be backported to 6.13 stable?

IMO these patches should be backported:
   https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e5c2bcc0cd47321d78bb4e865d7857304139f95d
   https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9bce6b5f8987678b9c6c1fe433af6b5fe41feadc

Thanks,
Milan


  reply	other threads:[~2025-03-19 18:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 15:18 [PATCH] block: cleanup and fix batch completion adding conditions Jens Axboe
2025-02-19  7:26 ` Shinichiro Kawasaki
2025-02-19 19:17   ` alan.adamson
2025-02-20  1:04     ` alan.adamson
2025-02-20  7:28       ` Shinichiro Kawasaki
2025-02-28 11:59 ` Ondrej Kozina
2025-02-28 14:08   ` Jens Axboe
2025-02-28 14:32     ` Ondrej Kozina
2025-03-04  9:25       ` Milan Broz
2025-03-11  3:03         ` Shinichiro Kawasaki
2025-03-11 14:59           ` Milan Broz
2025-03-11 15:00             ` Jens Axboe
2025-03-19 18:54               ` Milan Broz [this message]
2025-03-12 11:17           ` Ondrej Kozina

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=38b3eb9b-6448-4684-9f47-f4b64e5415cd@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=alan.adamson@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=okozina@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=shinichiro.kawasaki@wdc.com \
    --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