From: Christoph Hellwig <hch@lst.de>
To: "J. Hart" <jfhart085@gmail.com>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, axboe@fb.com, sagi@grimberg.me
Subject: Re: nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed
Date: Fri, 16 Dec 2022 07:39:53 +0100 [thread overview]
Message-ID: <20221216063953.GA24390@lst.de> (raw)
In-Reply-To: <581e0725-93cb-b796-e2c6-455737cc8ea1@gmail.com>
On Fri, Dec 16, 2022 at 07:30:55AM +0900, J. Hart wrote:
> I've tried the obvious ones and that didn't help either. I guess I'll have
> to give up on it and return it as defective. I'll go back to normal
> operation and to try and find a controller/device combination that works
> with the linux driver if there are any.
So on the hand I agree with Keith that the device seems really broken.
On the other hand the fact that source file system on another device
sees corruption even with the iommu enabled is something that looks
scrary. Even if ultimatively caused by the device somehow, that seems
like the kernel is part of the corruption. And I have absolutely no
idea how. A KASAN run on the device might be helpful, but I'm also
reluctant to ask a reported to run more reproducers and something that
corrupts his data.
next prev parent reply other threads:[~2022-12-16 6:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:38 nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed J. Hart
2022-12-15 8:23 ` Christoph Hellwig
2022-12-15 9:07 ` J. Hart
2022-12-15 9:09 ` Christoph Hellwig
2022-12-15 9:15 ` J. Hart
2022-12-15 13:33 ` J. Hart
2022-12-15 17:34 ` Keith Busch
2022-12-15 22:30 ` J. Hart
2022-12-16 6:39 ` Christoph Hellwig [this message]
2022-12-16 19:08 ` Keith Busch
2023-01-18 10:27 ` Mark Ruijter
2022-12-16 23:16 ` Keith Busch
2022-12-17 1:28 ` J. Hart
2022-12-19 14:41 ` Keith Busch
2022-12-20 1:10 ` J. Hart
2022-12-20 16:56 ` Keith Busch
2022-12-21 7:50 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-12-17 12:07 J. Hart
2022-12-17 15:07 J. Hart
2022-12-17 16:14 J. Hart
2022-12-17 21:57 J. Hart
2022-12-18 6:20 J. Hart
2022-12-18 12:08 J. Hart
2022-12-19 14:45 ` Keith Busch
2022-12-19 23:40 ` J. Hart
2022-12-20 18:10 ` Keith Busch
2022-12-20 14:04 ` J. Hart
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=20221216063953.GA24390@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=jfhart085@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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