public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: Huang Ying <ying.huang@intel.com>, Jiri Kosina <jkosina@suse.cz>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>,
	x86-ml <x86@kernel.org>
Subject: Re: [LKP] [x86/mm/ASLR] f47233c2d34: WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:63 __ioremap_check_ram+0x445/0x4a0()
Date: Thu, 26 Feb 2015 12:12:50 +0100	[thread overview]
Message-ID: <20150226111250.GA32024@gmail.com> (raw)
In-Reply-To: <20150226103040.GA3573@pd.tnic>


* Borislav Petkov <bp@suse.de> 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

  reply	other threads:[~2015-02-26 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  5:37 [LKP] [x86/mm/ASLR] f47233c2d34: WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:63 __ioremap_check_ram+0x445/0x4a0() Huang Ying
2015-02-26 10:30 ` Borislav Petkov
2015-02-26 11:12   ` Ingo Molnar [this message]
2015-02-26 12:16     ` Borislav Petkov
2015-02-28 10:50       ` Borislav Petkov
2015-02-28 19:20         ` Matt Fleming
2015-02-28 19:52           ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150226111250.GA32024@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox