Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753866AbbLIS7n (ORCPT ); Wed, 9 Dec 2015 13:59:43 -0500 Received: from mail-io0-f172.google.com ([209.85.223.172]:33470 "EHLO mail-io0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753457AbbLIS7k (ORCPT ); Wed, 9 Dec 2015 13:59:40 -0500 MIME-Version: 1.0 In-Reply-To: <1449300220-30108-1-git-send-email-kuleshovmail@gmail.com> References: <1449300220-30108-1-git-send-email-kuleshovmail@gmail.com> Date: Wed, 9 Dec 2015 10:59:40 -0800 Message-ID: Subject: Re: [PATCH] mm/memblock: use memblock_insert_region() for the empty array From: Tyler Baker To: Alexander Kuleshov Cc: Andrew Morton , Tony Luck , Tang Chen , Pekka Enberg , Wei Yang , Linux MM , "linux-kernel@vger.kernel.org" , "Kevin's boot bot" , Dan Williams Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1040 Lines: 24 On 4 December 2015 at 23:23, Alexander Kuleshov wrote: > We have the special case for an empty array in the memblock_add_range() > function. In the same time we have almost the same functional in the > memblock_insert_region() function. Let's use the memblock_insert_region() > instead of direct initialization. > > Signed-off-by: Alexander Kuleshov Just to add on to the report from Dan, the kernelci.org boot bot has also detected ~65 new boot failures in next-20151209[1], which have been bisected to this patch[2]. It doesn't revert cleanly, so I'm going to try to clean it up by hand and see if it resolves the issue. Cheers, Tyler [1] http://kernelci.org/boot/all/job/next/kernel/next-20151209/ [2] http://hastebin.com/ufiwonuraw.vhdl -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/