From: Keith Busch <kbusch@kernel.org>
To: Leo Stone <leocstone@gmail.com>
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
csander@purestorage.com, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org,
syzbot+ff4aab278fa7e27e0f9e@syzkaller.appspotmail.com
Subject: Re: [PATCH v3] nvmet: Don't overflow subsysnqn
Date: Fri, 27 Dec 2024 14:15:13 -0700 [thread overview]
Message-ID: <Z28Y4XRagAT9DB3z@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20241218185000.17920-2-leocstone@gmail.com>
On Wed, Dec 18, 2024 at 10:49:57AM -0800, Leo Stone wrote:
> nvmet_root_discovery_nqn_store treats the subsysnqn string like a fixed
> size buffer, even though it is dynamically allocated to the size of the
> string.
>
> Create a new string with kstrndup instead of using the old buffer.
Thanks, applied to nvme-6.13.
prev parent reply other threads:[~2024-12-27 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 18:49 [PATCH v3] nvmet: Don't overflow subsysnqn Leo Stone
2024-12-19 5:34 ` Christoph Hellwig
2024-12-24 10:40 ` Sagi Grimberg
2024-12-27 21:15 ` Keith Busch [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=Z28Y4XRagAT9DB3z@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=csander@purestorage.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=leocstone@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=syzbot+ff4aab278fa7e27e0f9e@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox