linux-kernel - Re: [PATCH] staging: tidspbridge

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]

Date:	Wed, 5 Jan 2011 12:05:31 +0200
From:	Felipe Contreras <felipe.contreras@...il.com>
To:	Fernando Guzman Lugo <fernando.lugo@...com>
Cc:	omar.ramirez@...com, gregkh@...e.de, rene.sapiens@...com,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	linux-omap@...r.kernel.org,
	Felipe Contreras <felipe.contreras@...ia.com>
Subject: Re: [PATCH] staging: tidspbridge - configure full L1 MMU range

On Wed, Jan 5, 2011 at 8:20 AM, Fernando Guzman Lugo
<fernando.lugo@...com> wrote:
> Otherwise a virtual address beyond of the L1 size is used,
> the MMU hardware will look into a memory that does not belong to
> L1 translation tables. IOW; the MMU would allow to access any
> memory, configured 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>

People rarely use ' - ' in the commit summary:
% git log --oneline -1000 | grep -e ' - ' | wc -l
32

Which means about only 3%. If you do the same on
drivers/staging/tidspbridge, you'll see that the only commits that
have that are from you.

staging: tidspbridge: configure full L1 MMU range

Other than that, I think this is is a critical bugfix, and should be
applied ASAP.

Cheers.

-- 
Felipe Contreras
--
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/