linux-kernel - Re: [PATCH 29/30] microblaze_mmu

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200904301553.47556.arnd@arndb.de>
Date:	Thu, 30 Apr 2009 15:53:46 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	monstr@...str.eu
Cc:	Christoph Hellwig <hch@...radead.org>,
	linux-kernel@...r.kernel.org, john.williams@...alogix.com
Subject: Re: [PATCH 29/30] microblaze_mmu_v1: stat.h MMU update

On Monday 27 April 2009, Michal Simek wrote:
> Arnd Bergmann wrote:
> > On Monday 27 April 2009, Michal Simek wrote:
> >>> st_size represents an off_t in user space, which is signed.
> >>> Just over half the existing architectures use signed types
> >>> for st_size, but for this (like Sam's suggestion for __u64),
> >>> I don't think it matters either way.
> >> OK. Is it mean that your structure is perfect? If yes,
> >> I'll recompile toolchain and do some more tests. 
> > 
> > Please wait for my full patches, which I am about to
> > post. I hope to get to the stage where literally none
> > of the ABI is defined in your own header files but
> > it all gets into the generic parts. I hope to get this
> > out within a few hours.
> 
> OK.

Any success so far with the patches I posted? I guess you
need to apply just the first of the three microblaze patches
in the series first to see if that works, before changing
the signal handling and syscall table as well.

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