[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f106fc33-4935-6f07-3e93-35bfd0d2434d@redhat.com>
Date: Wed, 24 Nov 2021 12:10:49 +0100
From: David Hildenbrand <david@...hat.com>
To: cgel.zte@...il.com, akpm@...ux-foundation.org
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
chiminghao <chi.minghao@....com.cn>,
Zeal Robot <zealci@....com.cn>
Subject: Re: [PATCH] mm: Use BUG_ON instead of if condition followed by BUG
On 24.11.21 04:08, cgel.zte@...il.com wrote:
> From: chiminghao <chi.minghao@....com.cn>
"mm/memory_hotplug: Use BUG_ON instead of if condition followed by BUG"
Would be better
>
> Fix the following coccinelle report:
> ./mm/memory_hotplug.c:2210:2-5:
> WARNING Use BUG_ON instead of if condition followed by BUG.
>
> Reported-by: Zeal Robot <zealci@....com.cn>
> Signed-off-by: chiminghao <chi.minghao@....com.cn>
> ---
> mm/memory_hotplug.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 3de7933e5302..aecb12bb7513 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -2212,8 +2212,7 @@ void __remove_memory(u64 start, u64 size)
> * trigger BUG() if some memory is not offlined prior to calling this
> * function
> */
> - if (try_remove_memory(start, size))
> - BUG();
> + BUG_ON(try_remove_memory(start, size));
> }
>
> /*
>
Acked-by: David Hildenbrand <david@...hat.com>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists