Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938417AbcKXJaH (ORCPT ); Thu, 24 Nov 2016 04:30:07 -0500 Received: from mail-qk0-f176.google.com ([209.85.220.176]:34251 "EHLO mail-qk0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935627AbcKXJaE (ORCPT ); Thu, 24 Nov 2016 04:30:04 -0500 MIME-Version: 1.0 In-Reply-To: <20161122142829.1776129-1-arnd@arndb.de> References: <20161122142829.1776129-1-arnd@arndb.de> From: Jakub Kicinski Date: Thu, 24 Nov 2016 01:30:03 -0800 Message-ID: Subject: Re: [PATCH] ARM: fix kmemleak for XIP_KERNEL To: Arnd Bergmann Cc: Russell King , Catalin Marinas , linux-s390@vger.kernel.org, Martin Schwidefsky , Heiko Carstens , Andrew Morton , Chris Brandt , Kees Cook , Nicolas Pitre , Chris Metcalf , linux-arm-kernel@lists.infradead.org, LKML 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: 1378 Lines: 37 On Tue, Nov 22, 2016 at 6:28 AM, Arnd Bergmann wrote: > The newly added check for RO_AFTER_INIT_DATA in kmemleak breaks ARM whenever > XIP_KERNEL is enabled: > > mm/kmemleak.o: In function `kmemleak_scan': > kmemleak.c:(.text.kmemleak_scan+0x2e4): undefined reference to `__end_data_ro_after_init' > kmemleak.c:(.text.kmemleak_scan+0x2e8): undefined reference to `__start_data_ro_after_init' > > This adds the start/end symbols for the section even in the case of having > no data in the section, to make the check work while keeping the architecture > specific override in one place. > > Fixes: d7c19b066dcf ("mm: kmemleak: scan .data.ro_after_init") > Signed-off-by: Arnd Bergmann > --- > The patch causing this was merged late into v4.9-rc, this one should > probably go there as well. > > I assume the same problem exists on s390, but I have not checked that. Hi Arnd! Sorry for breaking things again :( The confusion must have been caused by going via different trees. Actually, Russell's commit is dated 6 days after mine so could as well be: Fixes: 2a3811068fbc ("ARM: Fix XIP kernels") Not that it matters. About s390 - I thought I took care of it in d7c19b066dcf ("mm: kmemleak: scan .data.ro_after_init"), do you see anything suspicious in the way I did it? I'll do some more s390 builds just to triple check. Sorry again, Kuba