From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754245Ab3BPTvZ (ORCPT ); Sat, 16 Feb 2013 14:51:25 -0500 Received: from mail-ve0-f173.google.com ([209.85.128.173]:50413 "EHLO mail-ve0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754129Ab3BPTvY (ORCPT ); Sat, 16 Feb 2013 14:51:24 -0500 MIME-Version: 1.0 In-Reply-To: References: <20130213111007.GA11367@gmail.com> <20130214144510.GC25282@gmail.com> <20130214145424.GA26071@gmail.com> <20130214150810.GA26095@gmail.com> <20130215114425.GD26955@gmail.com> From: Linus Torvalds Date: Sat, 16 Feb 2013 11:51:03 -0800 X-Google-Sender-Auth: SA466uGPDax-68C1BwNl1Ea6tlU Message-ID: Subject: Re: [-rc7 regression] Buggy commit: "mm: use aligned zone start for pfn_to_bitidx calculation" To: Yinghai Lu Cc: Ingo Molnar , Greg KH , Thomas Gleixner , Linux Kernel Mailing List , Jens Axboe , Alexander Viro , "Theodore Ts'o" , "H. Peter Anvin" , Laura Abbott , Mel Gorman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 16, 2013 at 11:38 AM, Yinghai Lu wrote: > > but you forgot to update setup_usemap() for SPARSEMEM Heh. I tried desperately to find a config to test my patch in, because I couldn't see how to even disable SPARSEMEM for my normal x86-64 build. But then I *only* tested it for that non-SPARSEMEM case, expecting that to be what showed any problems. The fact that I didn't bother testing my normal config is a bit ironic. But I'd still like verification that it actually fixes Ingo's issue. It *looks* like it should, and it would explain the potential for memory corruption, but perhaps Ingo's odd lock-up is due to something really subtle and unrelated to the actual allocation size. Linus