From: Vlastimil Babka <vbabka@suse.cz>
To: Markus Elfring <Markus.Elfring@web.de>,
kernel-janitors@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Kosaki Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Mel Gorman <mgorman@suse.de>
Cc: cocci@inria.fr, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/mempolicy: Fix exception handling in shared_policy_replace()
Date: Fri, 24 Mar 2023 18:30:02 +0100 [thread overview]
Message-ID: <22a1ec75-155a-2392-ce39-4bca3fc081eb@suse.cz> (raw)
In-Reply-To: <6e9ca062-939b-af96-c8ff-56ad485d6e79@web.de>
Your patch doesn't apply, seems like it uses spaces instead of tabs. Also I
can't use 'b4' to download it as there are multiple different patches using
the same message-id:
https://lore.kernel.org/all/6e9ca062-939b-af96-c8ff-56ad485d6e79@web.de/
Re: subject, I don't see a bug that this would fix. You could say it's
"cleanup" and this function could use one, but for a cleanup it's not
improving the situation much.
On 3/23/23 18:30, Markus Elfring wrote:
> Date: Thu, 23 Mar 2023 18:18:59 +0100
>
> The label “err_out” was used to jump to another pointer check despite of
> the detail in the implementation of the function “shared_policy_replace”
> that it was determined already that a corresponding variable contained a
> null pointer because of a failed call of the function “kmem_cache_alloc”.
>
> 1. Use more appropriate labels instead.
>
> 2. The implementation of the function “mpol_put” contains a pointer check
> for its single input parameter.
> Thus delete a redundant check in the caller.
>
>
> This issue was detected by using the Coccinelle software.
>
> Fixes: 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 ("mm: mempolicy: Convert shared_policy mutex to spinlock")
Again this is not a fix.
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
> mm/mempolicy.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index a256a241fd1d..fb0485688dcb 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -2736,13 +2736,12 @@ static int shared_policy_replace(struct shared_policy *sp, unsigned long start,
> sp_insert(sp, new);
> write_unlock(&sp->lock);
> ret = 0;
> +put_mpol:
> + mpol_put(mpol_new);
>
> -err_out:
> - if (mpol_new)
> - mpol_put(mpol_new);
> if (n_new)
> kmem_cache_free(sn_cache, n_new);
> -
> +exit:
> return ret;
>
> alloc_new:
> @@ -2750,10 +2749,10 @@ static int shared_policy_replace(struct shared_policy *sp, unsigned long start,
> ret = -ENOMEM;
> n_new = kmem_cache_alloc(sn_cache, GFP_KERNEL);
> if (!n_new)
> - goto err_out;
> + goto exit;
Just "return ret" and no need for exit label?
> mpol_new = kmem_cache_alloc(policy_cache, GFP_KERNEL);
> if (!mpol_new)
> - goto err_out;
> + goto put_mpol;
We are doing this because mpol_new == NULL, so we know there's no reason to
do mpol_put(), we could jump to the freeing of n_new.
> atomic_set(&mpol_new->refcnt, 1);
> goto restart;
> }
> --
> 2.40.0
>
>
>
next prev parent reply other threads:[~2023-03-24 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f9303bdc-b1a7-be5e-56c6-dfa8232b8b55@web.de>
2023-03-23 17:30 ` Markus Elfring
2023-03-24 17:30 ` Vlastimil Babka [this message]
2023-03-24 18:03 ` Markus Elfring
2023-03-25 18:30 ` [PATCH] selftests: cgroup: Fix exception handling in test_memcg_oom_group_score_events() Markus Elfring
2023-03-25 19:24 ` Lorenzo Stoakes
2023-03-26 8:15 ` Markus Elfring
2023-03-26 21:39 ` David Vernet
2023-03-27 5:56 ` Markus Elfring
2023-03-27 9:13 ` David Vernet
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=22a1ec75-155a-2392-ce39-4bca3fc081eb@suse.cz \
--to=vbabka@suse.cz \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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