From: emilne@redhat.com (Ewan D. Milne)
Subject: [PATCH] nvme: initialize hostid uuid in nvmf_host_default to not leak kernel memory
Date: Wed, 10 Jan 2018 14:39:35 -0500 [thread overview]
Message-ID: <1515613175.3913.105.camel@localhost.localdomain> (raw)
In-Reply-To: <20180109164252.GD15154@localhost.localdomain>
On Tue, 2018-01-09@09:42 -0700, Keith Busch wrote:
>
> Thanks for the report and the fix. It'd still be good to use the kzalloc
> variant in addition to this.
Yes, thanks. Good point.
kmalloc() is used elsewhere as well, so maybe another patch?
-Ewan
prev parent reply other threads:[~2018-01-10 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 15:20 [PATCH] nvme: initialize hostid uuid in nvmf_host_default to not leak kernel memory Johannes Thumshirn
2018-01-09 15:20 ` Johannes Thumshirn
2018-01-09 16:42 ` Keith Busch
2018-01-09 16:42 ` Keith Busch
2018-01-09 16:42 ` Christoph Hellwig
2018-01-09 16:42 ` Christoph Hellwig
2018-01-10 19:39 ` Ewan D. Milne [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=1515613175.3913.105.camel@localhost.localdomain \
--to=emilne@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.