Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753642AbbBZLM5 (ORCPT ); Thu, 26 Feb 2015 06:12:57 -0500 Received: from mail-wg0-f43.google.com ([74.125.82.43]:37304 "EHLO mail-wg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752752AbbBZLM4 (ORCPT ); Thu, 26 Feb 2015 06:12:56 -0500 Date: Thu, 26 Feb 2015 12:12:50 +0100 From: Ingo Molnar To: Borislav Petkov Cc: Huang Ying , Jiri Kosina , LKML , LKP ML , x86-ml Subject: Re: [LKP] [x86/mm/ASLR] f47233c2d34: WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:63 __ioremap_check_ram+0x445/0x4a0() Message-ID: <20150226111250.GA32024@gmail.com> References: <1424929021.10337.24.camel@intel.com> <20150226103040.GA3573@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150226103040.GA3573@pd.tnic> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 923 Lines: 28 * Borislav Petkov wrote: > thanks for the report. > > So, AFAICT, this is caused by ksysfs ioremapping struct > setup_data for a short time so that it can count it and > show it in /sys/kernel/boot_params/setup_data/* > > And, of course, the setup_data thing which we're using > for kaslr param passing is RAM and ioremap complains. > > And currently I don't have a good idea how to fix it. > Perhaps introduce an ioremap_* something which suppresses > the warning as we're going to iounmap() right afterwards > but that's ugly. Why is it ioremap()-ed to begin with, why cannot the kernel access its own data structure in RAM directly? Thanks, Ingo -- 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/