linux-kernel - Re: [PATCH] m68k/sun3: Fix virtual addresses of clock and interrupt register

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: <20150925104553.GA22917@alpha.franken.de>
Date:	Fri, 25 Sep 2015 12:45:53 +0200
From:	Tom Bogendoerfer <tsbogend@...ha.franken.de>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Alexander Kuleshov <kuleshovmail@...il.com>,
	Sam Creasey <sammy@...my.net>,
	linux-m68k <linux-m68k@...ts.linux-m68k.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] m68k/sun3: Fix virtual addresses of clock and interrupt
 register

On Fri, Sep 25, 2015 at 09:21:34AM +0200, Geert Uytterhoeven wrote:
> On Mon, Sep 14, 2015 at 11:40 AM, Alexander Kuleshov
> <kuleshovmail@...il.com> wrote:
> > The MMU base is 32 bits size - 0xfe000000, seems that we missed
> > one zero in the definition of the clock and interrupt register
> > addresses.
> 
> Thanks for your patch!
> 
> Have you tested this?
> 
> This means enabling/disabling interrupts never worked on Sun 3, which
> I find a bit difficult to believe.
> There are other 0x0f?????? addresses in arch/m68k/sun3/mmu_emu.c.

which are the correct one. Sun3 MMU doesn't even handle full 32bit
addresses, it's only capable of 28 bits. That's the reason why normal
m68k linux user space binaries can't work.

So this patch is broken. And I'm sure the unpatched version works.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]
--
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/