From: Ralph Campbell <rcampbell@nvidia.com>
To: Wei Yongjun <weiyongjun1@huawei.com>, <jglisse@redhat.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>, Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH -next] mm/hmm/test: fix error return code in hmm_dmirror_init()
Date: Mon, 11 May 2020 10:20:17 -0700 [thread overview]
Message-ID: <b8da4751-ea8a-7e4d-9a6c-ee6bd7038eb7@nvidia.com> (raw)
In-Reply-To: <20200509030234.14747-1-weiyongjun1@huawei.com>
On 5/8/20 8:02 PM, Wei Yongjun wrote:
> Fix to return negative error code -ENOMEM from the alloc_page() error
> handling case instead of 0, as done elsewhere in this function.
>
> Fixes: 5d5e54be8a1e ("mm/hmm/test: add selftest driver for HMM")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
Looks good, thanks!
Reviewed-by: Ralph Campbell <rcampbell@nvidia.com>
> ---
> lib/test_hmm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/lib/test_hmm.c b/lib/test_hmm.c
> index 00bca6116f93..b4d9434e49e7 100644
> --- a/lib/test_hmm.c
> +++ b/lib/test_hmm.c
> @@ -1119,8 +1119,10 @@ static int __init hmm_dmirror_init(void)
> * make the code here simpler (i.e., we need a struct page for it).
> */
> dmirror_zero_page = alloc_page(GFP_HIGHUSER | __GFP_ZERO);
> - if (!dmirror_zero_page)
> + if (!dmirror_zero_page) {
> + ret = -ENOMEM;
> goto err_chrdev;
> + }
>
> pr_info("HMM test module loaded. This is only for testing HMM.\n");
> return 0;
>
>
>
next prev parent reply other threads:[~2020-05-11 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 3:02 [PATCH -next] mm/hmm/test: fix error return code in hmm_dmirror_init() Wei Yongjun
2020-05-11 17:20 ` Ralph Campbell [this message]
2020-05-12 19:59 ` Jason Gunthorpe
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=b8da4751-ea8a-7e4d-9a6c-ee6bd7038eb7@nvidia.com \
--to=rcampbell@nvidia.com \
--cc=hulkci@huawei.com \
--cc=jglisse@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=weiyongjun1@huawei.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;
as well as URLs for NNTP newsgroup(s).