[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151015100333.GD4267@pd.tnic>
Date: Thu, 15 Oct 2015 12:03:34 +0200
From: Borislav Petkov <bp@...en8.de>
To: Dave Young <dyoung@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
jerry_hoemann@...com, Jiri Kosina <jkosina@...e.cz>,
Joerg Roedel <jroedel@...e.de>,
Juergen Gross <jgross@...e.com>,
Mark Salter <msalter@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
WANG Chao <chaowang@...hat.com>, x86-ml <x86@...nel.org>
Subject: Re: [PATCH 4/5] x86/setup/crash: Check memblock_reserve() retval
On Thu, Oct 15, 2015 at 05:18:26PM +0800, Dave Young wrote:
> Seems there's no checking for other callback to memblock_reserve in setup.c
> Need another cleanup?
True story. It sure does.
> BTW, a further cleanup is reasonable to me, there's a lot of below patter:
> memblock_find_in_range
> error checking
> memblock_reserve
> error checking
>
> So a new function memblock_reserve_in_range is reasonable.
Well, in some of the callsites, the first "error checking" issues
a specific message, depending on the subsystem. The following
memblock_reserve() is mostly unchecked though. At least that should be
fixed...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists