From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH -next] nvmet: fix return value check in nvmet_subsys_alloc()
Date: Tue, 12 Jul 2016 08:34:13 -0700 [thread overview]
Message-ID: <57850DF5.2090209@kernel.dk> (raw)
In-Reply-To: <1467806529-23712-1-git-send-email-weiyj_lk@163.com>
On 07/06/2016 05:02 AM, weiyj_lk@163.com wrote:
> From: Wei Yongjun <yongjun_wei at trendmicro.com.cn>
>
> In case of error, the function kstrndup() returns NULL pointer
> not ERR_PTR(). The IS_ERR() test in the return value check
> should be replaced with NULL test.
Added for 4.8, thanks.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: weiyj_lk@163.com, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>
Cc: Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH -next] nvmet: fix return value check in nvmet_subsys_alloc()
Date: Tue, 12 Jul 2016 08:34:13 -0700 [thread overview]
Message-ID: <57850DF5.2090209@kernel.dk> (raw)
In-Reply-To: <1467806529-23712-1-git-send-email-weiyj_lk@163.com>
On 07/06/2016 05:02 AM, weiyj_lk@163.com wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> In case of error, the function kstrndup() returns NULL pointer
> not ERR_PTR(). The IS_ERR() test in the return value check
> should be replaced with NULL test.
Added for 4.8, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2016-07-12 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 12:02 [PATCH -next] nvmet: fix return value check in nvmet_subsys_alloc() weiyj_lk
2016-07-06 12:02 ` weiyj_lk
2016-07-08 22:27 ` J Freyensee
2016-07-08 22:27 ` J Freyensee
2016-07-12 15:34 ` Jens Axboe [this message]
2016-07-12 15:34 ` Jens Axboe
2016-07-13 10:37 ` Sagi Grimberg
2016-07-13 10:37 ` Sagi Grimberg
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=57850DF5.2090209@kernel.dk \
--to=axboe@kernel.dk \
/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.