linux-kernel - Re: [PATCH 44/57] microblaze

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, 25 Mar 2009 00:06:10 +1000
From:	John Williams <john.williams@...alogix.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	monstr@...str.eu, linux-kernel@...r.kernel.org,
	Remis Lima Baima <remisbaima@...il.com>
Subject: Re: [PATCH 44/57] microblaze_v7: termbits.h termios.h

Hi Arnd,

On Tue, Mar 24, 2009 at 11:57 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Tuesday 24 March 2009, Michal Simek wrote:
>> > I haven't gotten around to posting them for review, but I still think
>> > it would be great if we can at least make sure they are identical
>> > so we can remove your versions as soon as we have the asm-generic ones.
>>
>> I tested it some min ago. I just take your termios.h and termbits.h from
>> asm-generic folder. I miss there only #include <asm/uaccess.h> in termion.h.
>>
>> Compilation is OK and kernel works with your files too. For me is easy to use
>> your version. If they are there, I'll use them.
>
> Ok. I did not just mean these specific files, but all the headers in
> general. I assume that you have not had a chance to look into the
> other header files, which is ok. Remis is currently cleaning up bits
> of the generic header files in Linux based on my work, and I asked
> him to look into your tree to see how much can be shared.
>
> Note that there is a problem of binary compatibility with certain headers.
> If e.g. the constants from termbits.h or some data structures slightly
> change, user space will still compile but no longer be compatible
> with other kernel versions, so this needs to be done very carefully.

We are viewing this kernel as a clean break from the past (2.6.20
maintained outside kernel.org).

There will be a new toolchain/glibc/uClibc built against these modern
kernel headers, so I think the binary compatibility issue will have
minimal impact on the existing userbase.  They will just have to
rebuild their apps.  In the space where MicroBlaze finds itself, it's
typical to rebuild an entire system image from source.  Certainly I'm
not aware of anyone moving RPMs around containing MicroBlaze binaries!

Regards,

John
-- 
John Williams,
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com  p: +61-7-30090663  f: +61-7-30090663
--
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/