linux-kernel - Re: [PATCHv2] staging: tidspbridge: configure full L1 MMU range

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] [day] [month] [year] [list]

Date:	Thu, 13 Jan 2011 19:39:19 -0600
From:	"Ramirez Luna, Omar" <omar.ramirez@...com>
To:	Fernando Guzman Lugo <fernando.lugo@...com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org, linux-omap@...r.kernel.org,
	Felipe Contreras <felipe.contreras@...ia.com>
Subject: Re: [PATCHv2] staging: tidspbridge: configure full L1 MMU range

Hi,

On Wed, Jan 5, 2011 at 3:25 PM, Fernando Guzman Lugo
<fernando.lugo@...com> wrote:
> From: Guzman Lugo, Fernando <fernando.lugo@...com>
>
> IVA MMU can manage up to 4GB of address space through its page tables,
> given that it's L1 is divided into 1MB sections it requires at least
> 16KB for its table which represents 4096 entries of 32 bits each.
>
> Previously, only 1GB was being handled by setting the page table size
> to 4KB, any virtual address beyond of the L1 size used, would fall
> into memory that does not belong to L1 translation tables, leading to
> unpredictable results.
>
> So, set the L1 table size to cover the entire MMU range (4GB) whether
> is meant to be used or not.
>
> Reported-by: Felipe Contreras <felipe.contreras@...ia.com>
> Signed-off-by: Fernando Guzman Lugo <fernando.lugo@...com>
> Signed-off-by: Felipe Contreras <felipe.contreras@...ia.com>

Nice fix, pushed to for-gkh-2.6.38 branch.

Regards,

Omar
--
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/