From: David Hildenbrand <david@redhat.com>
To: xiujianfeng <xiujianfeng@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Binyi Han <dantengknight@gmail.com>
Subject: Re: [PATCH] mm/secretmem: remove reduntant return value
Date: Tue, 20 Sep 2022 15:22:38 +0200 [thread overview]
Message-ID: <7f1cfee4-c6de-ea59-0aa9-9bd55054fb22@redhat.com> (raw)
In-Reply-To: <c4e99ea3-302d-b173-27f1-92c38ddaca8c@huawei.com>
On 20.09.22 14:35, xiujianfeng wrote:
> Hi,
>
> 在 2022/9/20 20:10, David Hildenbrand 写道:
>> On 20.09.22 03:22, Xiu Jianfeng wrote:
>>> The return value @ret is always 0, so remove it and return 0 directly.
>>>
>>> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
>>> ---
>>> mm/secretmem.c | 6 ++----
>>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/mm/secretmem.c b/mm/secretmem.c
>>> index 6a44efb673b2..04c3ac9448a1 100644
>>> --- a/mm/secretmem.c
>>> +++ b/mm/secretmem.c
>>> @@ -278,10 +278,8 @@ static struct file_system_type secretmem_fs = {
>>> static int __init secretmem_init(void)
>>> {
>>> - int ret = 0;
>>> -
>>> if (!secretmem_enable)
>>> - return ret;
>>> + return 0;
>>> secretmem_mnt = kern_mount(&secretmem_fs);
>>> if (IS_ERR(secretmem_mnt))
>>
>> On top of which tree is that?
>>
>> 6.0-rc6 has here:
>>
>> if (IS_ERR(secretmem_mnt))
>> ret = PTR_ERR(secretmem_mnt);
>>
> Sorry, it's on linux-next tree, I should have used [PATCH -next]:)
>
Maybe this change should be squashed into the patch from Binyi directly:
commit 4eb5bbde3ccb710d3b85bfb13466612e56393369 (mm/mm-hotfixes-stable)
Author: Binyi Han <dantengknight@gmail.com>
Date: Sun Sep 4 00:46:47 2022 -0700
mm: fix dereferencing possible ERR_PTR
Smatch checker complains that 'secretmem_mnt' dereferencing possible
ERR_PTR(). Let the function return if 'secretmem_mnt' is ERR_PTR, to
avoid deferencing it.
Link: https://lkml.kernel.org/r/20220904074647.GA64291@cloud-MacBookPro
Fixes: 1507f51255c9f ("mm: introduce memfd_secret system call to create "secret" memory areas")
Signed-off-by: Binyi Han <dantengknight@gmail.com>
Reviewed-by: Andrew Morton <akpm@linux-foudation.org>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-09-20 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 1:22 Xiu Jianfeng
2022-09-20 12:10 ` David Hildenbrand
2022-09-20 12:35 ` xiujianfeng
2022-09-20 13:22 ` David Hildenbrand [this message]
2022-09-20 13:28 ` xiujianfeng
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=7f1cfee4-c6de-ea59-0aa9-9bd55054fb22@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dantengknight@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xiujianfeng@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