[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240307170901.GBZen0re6AvpscLaTM@fat_crate.local>
Date: Thu, 7 Mar 2024 18:09:01 +0100
From: Borislav Petkov <bp@...en8.de>
To: Sohil Mehta <sohil.mehta@...el.com>
Cc: Tony Luck <tony.luck@...el.com>, "Naik, Avadhut" <avadnaik@....com>,
Yazen Ghannam <yazen.ghannam@....com>, x86@...nel.org,
linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] x86/mce: Dynamically size space for machine check
records
On Thu, Mar 07, 2024 at 08:59:53AM -0800, Sohil Mehta wrote:
> I was about the suggest the same thing and maybe slightly more. By
> initializing ret when really needed, I find the code a bit easier to
> follow. No strong preference here.
Except that "really needed" is done this way:
> diff --git a/arch/x86/kernel/cpu/mce/genpool.c
> b/arch/x86/kernel/cpu/mce/genpool.c
> index cadf28662a70..83a01d20bbd9 100644
> --- a/arch/x86/kernel/cpu/mce/genpool.c
> +++ b/arch/x86/kernel/cpu/mce/genpool.c
> @@ -118,22 +118,21 @@ int mce_gen_pool_add(struct mce *mce)
>
> static int mce_gen_pool_create(void)
> {
> - int mce_numrecords, mce_poolsz, order;
> + int mce_numrecords, mce_poolsz, order, ret;
> struct gen_pool *tmpp;
> - int ret = -ENOMEM;
> void *mce_pool;
>
ret = -ENOMEM;
> order = order_base_2(sizeof(struct mce_evt_llist));
> tmpp = gen_pool_create(order, -1);
> if (!tmpp)
> - return ret;
> + return -ENOMEM;
>
ret = -ENOMEM;
> mce_numrecords = max(MCE_MIN_ENTRIES, num_possible_cpus() * MCE_PER_CPU);
> mce_poolsz = mce_numrecords * (1 << order);
> mce_pool = kmalloc(mce_poolsz, GFP_KERNEL);
> if (!mce_pool) {
> gen_pool_destroy(tmpp);
> - return ret;
> + return -ENOMEM;
before each block, so that it is clear what this particular block is
going to return on error.
But those assignments get redundant so the current way is fine, I'd say.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists