From: "Nadolski, Edmund" <edmund.nadolski@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
Edmund Nadolski <edmund.nadolski@intel.com>,
linux-nvme@lists.infradead.org, kbusch@kernel.org
Subject: Re: [PATCH 1/2] nvme: remove unused return code from nvme_alloc_ns
Date: Mon, 25 Nov 2019 09:46:08 -0700 [thread overview]
Message-ID: <221e4352-7fab-abea-9f43-2cd1df60dbaa@intel.com> (raw)
In-Reply-To: <1ca1b4c3-8c42-c728-d987-18821f83088a@suse.de>
On 11/25/2019 9:09 AM, Johannes Thumshirn wrote:
> On 25/11/2019 17:06, Edmund Nadolski wrote:
>> The return code of nvme_alloc_ns is never used, so change it
>> to void.
>
> Oh no, please do it the other way round, check the return value of
> nvme_alloc_ns() and handle error properly.
>
> nvme_alloc_ns() is doing memory allocations and these can fail (although
> less likely because of the GFP_KERNEL allocations).
I considered that, tho it looked to me like the caller (nvme_validate_ns) and
its callers (nvme_scan_ns_list, nvme_scan_ns_sequential) don't really care,
and intend simply to continue on regardless of memory alloc failure(s).
I can either add the -ENOMEM handling, or clarify the caller's intent w/some
comments. Which is the way to go?
Thanks,
Ed
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-11-25 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 16:06 [PATCH 0/2] A few code cleanups Edmund Nadolski
2019-11-25 16:06 ` [PATCH 1/2] nvme: remove unused return code from nvme_alloc_ns Edmund Nadolski
2019-11-25 16:09 ` Johannes Thumshirn
2019-11-25 16:46 ` Nadolski, Edmund [this message]
2019-11-25 17:06 ` Keith Busch
2019-11-26 4:01 ` Chaitanya Kulkarni
2019-11-26 16:47 ` Christoph Hellwig
2019-11-25 16:06 ` [PATCH 2/2] nvme: else following return is not needed Edmund Nadolski
2019-11-26 16:48 ` Christoph Hellwig
2019-11-26 17:38 ` Keith Busch
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=221e4352-7fab-abea-9f43-2cd1df60dbaa@intel.com \
--to=edmund.nadolski@intel.com \
--cc=jthumshirn@suse.de \
--cc=kbusch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox