From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Guangwu Zhang <guazhang@redhat.com>,
Ming Lei <ming.lei@redhat.com>,
Oleg Solovyov <mcpain@altlinux.org>
Subject: Re: stack smashing detected with 'nvme sanitize-log /dev/nvme0'
Date: Mon, 28 Aug 2023 11:21:55 +0200 [thread overview]
Message-ID: <20230828092155.GC30603@lst.de> (raw)
In-Reply-To: <j4azjg6k4cg3tynmvyl3qqcd7imcoaisy35ssqob34cw3ox32g@qk7dmqt72vbx>
On Fri, Aug 25, 2023 at 08:36:50AM +0200, Daniel Wagner wrote:
> Okay, let's ignore the regression argument then. But what about the fact
> we are asking for 512 bytes via the kernels API and get too much data?
> Isn't this something we should address? I mean this forces all users of
> this kernel API allocate enough large buffers to handle this device.
There isn't really much the kernel can do except for using an IOMMU
when available to protect itself from this, but that will mean we're
shutting down the device when it does that.
The device just seems completely broken unfortunately.
next prev parent reply other threads:[~2023-08-28 9:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 11:52 stack smashing detected with 'nvme sanitize-log /dev/nvme0' Daniel Wagner
2023-07-26 13:16 ` Christoph Hellwig
2023-08-21 13:37 ` Daniel Wagner
2023-08-21 15:11 ` Keith Busch
2023-08-22 7:55 ` Daniel Wagner
2023-08-23 15:37 ` Keith Busch
2023-08-25 6:36 ` Daniel Wagner
2023-08-28 9:21 ` Christoph Hellwig [this message]
2023-09-25 15:09 ` Daniel Wagner
2023-09-25 15:19 ` Christoph Hellwig
2023-08-28 9:20 ` Christoph Hellwig
2023-08-29 13:29 ` Keith Busch
2023-08-28 9:18 ` Christoph Hellwig
2023-07-27 1:30 ` Ming Lei
2023-07-27 1:37 ` Guangwu Zhang
2023-07-27 7:23 ` Daniel Wagner
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=20230828092155.GC30603@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=guazhang@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mcpain@altlinux.org \
--cc=ming.lei@redhat.com \
/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.