All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Keith Busch" <kbusch@kernel.org>
Cc: <linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	"Diederik de Haas" <didi.debian@cknow.org>
Subject: Re: [BUG report] kernel warnings with Samsung 970 EVO 2TB SSD
Date: Mon, 18 Aug 2025 23:20:00 +0200	[thread overview]
Message-ID: <DC5V8VGBDFQ8.3SZ2OASX2W75E@cknow.org> (raw)
In-Reply-To: <DC5UKZ9F6CQZ.2NDFY4S322T2G@cknow.org>

[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

On Mon Aug 18, 2025 at 10:48 PM CEST, Diederik de Haas wrote:
> On Mon Aug 18, 2025 at 8:58 PM CEST, Keith Busch wrote:
>> On Sat, Aug 16, 2025 at 04:11:00PM +0200, Diederik de Haas wrote:
>>> On Sat Aug 16, 2025 at 3:20 PM CEST, Keith Busch wrote:
>>> 
>>> The other kernel warning is this:
>>> 
>>>   nvme nvme0: using unchecked data buffer
>>> 
>>> The SUBNQN message appears every time, this one appears often, but not
>>> always.
>>
>> That one means you've sent a user space passthrough command to a device
>> that doesn't support SGL DMA. Without that, the nvme protocol uses
>> implicitly sized DMA that the driver can't be sure is accurate. The user
>> could theoretically provide a short buffer that can corrupt memory if
>> done by accident, or be used as an attack vector if done by malicious
>> software.
>>
>> This is also not something to worry about unless you run malicious or
>> buggy software.
>
> I would be surprised if I was running malicious software, but pretty
> much all software has bugs, so that's ofc possible.
> ...
>
> Uninstalled the 3 programs from R5S that showed up the most around the
> warning message and it's still there. 
> Would 'dyndbg' be helpful to determine what program is buggy?
  
Looks like I found the 'winner': udisks2 (package)

I uninstalled that and in the 10 boots after that, I did not see the
message. Installed it again (without Recommends) and it was back on the
first (re)boot.

Thanks!

Cheers,
  Diederik

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2025-08-18 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 11:40 [BUG report] kernel warnings with Samsung 970 EVO 2TB SSD Diederik de Haas
2025-08-16 13:20 ` Keith Busch
2025-08-16 14:11   ` Diederik de Haas
2025-08-18 18:58     ` Keith Busch
2025-08-18 20:48       ` Diederik de Haas
2025-08-18 21:20         ` Diederik de Haas [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=DC5V8VGBDFQ8.3SZ2OASX2W75E@cknow.org \
    --to=didi.debian@cknow.org \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.