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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <49F9B13C.3060008@monstr.eu>
Date:	Thu, 30 Apr 2009 16:10:04 +0200
From:	Michal Simek <monstr@...str.eu>
To:	Arnd Bergmann <arnd@...db.de>
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

Arnd Bergmann wrote:
> 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.

I looked at there are two things together. Header cleanup and syscall cleanup.
For both I have problems.
1. header cleanup -> some of them is only moving to generic location -> that's no problem
2. header cleanup -> some of them is pain because I have to recompile toolchain
that's should be a big deal but after recompilation kernel, user apps I am getting some problems.
3. syscall cleanup -> we still have old libc and I can't simple remove ancient syscalls

I would like to test all of them but I can't do too fast.
I am trying to cleanup uaccess.h troubles and I have some changes about context switch change
but this work only on MMU and I haven't had a time to fix it on noMMU.
I am fighting with old code where I don't have any information about.

I have your changes in my queue and they inspired me to do things better and I hope that
I will be able to use all of them.

Thanks,
Michal

> 	Arnd <><

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
--
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/