lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1507211620250.18576@nanos>
Date:	Tue, 21 Jul 2015 16:31:12 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Toshi Kani <toshi.kani@...com>
cc:	mingo@...hat.com, hpa@...or.com, akpm@...ux-foundation.org,
	travis@....com, roland@...estorage.com, dan.j.williams@...el.com,
	mcgrof@...e.com, x86@...nel.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH RESEND 2/3] mm, x86: Remove region_is_ram() call from
 ioremap

On Thu, 16 Jul 2015, Toshi Kani wrote:
> Note, removing the call to region_is_ram() is also necessary to
> fix bugs in region_is_ram().  walk_system_ram_range() requires
> RAM ranges be page-aligned in the iomem_resource table to work
> properly.  This restriction has allowed multiple ioremaps to RAM
> (setup_data) which are page-unaligned.  Using fixed region_is_ram()
> will cause these callers to start failing.

Which callers? 

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ