From: AlanCui4080 <me@alancui.cc>
To: linux-nvme@lists.infradead.org
Subject: Non-SGL transport mode warnings are set to dev_warn_once will cause confusion
Date: Thu, 09 Apr 2026 16:46:37 +0800 [thread overview]
Message-ID: <4770779.LvFx2qVVIh@alanarchdesktop> (raw)
Hi,
[ 49.108397] nvme nvme0: using unchecked data buffer
See 6fad84a (nvme-pci: use sgls for all user requests if possible). In the
kernel, those warnings are printed using `dev warn once`. This means that if
multiple devices in the system do not support SGLs (most consumer-grade
devices do not support them), only one warning for only one device will be
printed.
This asymmetry can be misleading to users. If all devices in the system report
the same issue, it might not be a problem, but if only one device reports it,
it might (especially since I have two identical drives). Is it possible to
move this warning to the device initialization phase so print it for each
device? Or, since we cannot resolve the issue of consumer-grade devices not
supporting SGL, should it be downgraded to an informational warning?
Alan.
next reply other threads:[~2026-04-09 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 8:46 AlanCui4080 [this message]
2026-04-09 14:36 ` Non-SGL transport mode warnings are set to dev_warn_once will cause confusion Keith Busch
2026-04-09 15:49 ` AlanCui4080
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=4770779.LvFx2qVVIh@alanarchdesktop \
--to=me@alancui.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox