linux-kernel - Re: [PATCH 2.6.19] m32r: Fix access error handler to pass full 32-bit address

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]

Message-id: <swf64cpz3pm.wl%takata.hirokazu@renesas.com>
Date:	Wed, 06 Dec 2006 20:03:17 +0900
From:	Hirokazu Takata <takata@...ux-m32r.org>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org, takata@...ux-m32r.org
Subject: Re: [PATCH 2.6.19] m32r: Fix access error handler to pass full 32-bit
 address

Hi, Andrew,

Sorry, I sent a patch with wrong title.
On m32r, ACE is an acronym of not "access error", but "access exception".

Please drop the previous patch entitled "[PATCH 2.6.19] m32r: Fix access
error handler to pass full 32-bit address".
I will resend a correct patch again.

Thanks,

From: Hirokazu Takata <takata@...ux-m32r.org>
Subject: [PATCH 2.6.19] m32r: Fix access error handler to pass full 32-bit address
Date: Wed, 06 Dec 2006 19:00:40 +0900
> Don't mask the lower 12-bit of the page fault address.
> 
> In the current m32r kernel implementation, we use an access error handler
> to detect page faults.
> In order to check userspace address in do_page_fault, we have to pass
> full 32-bit address to do_page_fault.
> 
> Signed-off-by: Hirokazu Takata <takata@...ux-m32r.org>
> ---
>  arch/m32r/kernel/entry.S |    2 --
>  arch/m32r/mm/fault.c     |    4 ++--
>  2 files changed, 2 insertions(+), 4 deletions(-)

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