linux-kernel - Re: [PATCH 07/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]

Message-Id: <200903232035.15100.arnd@arndb.de>
Date:	Mon, 23 Mar 2009 20:35:14 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	monstr@...str.eu
Cc:	linux-kernel@...r.kernel.org, john.williams@...alogix.com
Subject: Re: [PATCH 07/57] microblaze_v7: Signal support

On Wednesday 18 March 2009, monstr@...str.eu wrote:
> From: Michal Simek <monstr@...str.eu>
> 
> 
> Signed-off-by: Michal Simek <monstr@...str.eu>
> ---
>  arch/microblaze/include/asm/signal.h |  165 +++++++++++
>  arch/microblaze/kernel/signal.c      |  536 ++++++++++++++++++++++++++++++++++
>  2 files changed, 701 insertions(+), 0 deletions(-)
>  create mode 100644 arch/microblaze/include/asm/signal.h
>  create mode 100644 arch/microblaze/kernel/signal.c

> From: Michal Simek <monstr@...str.eu>
>
>
> Signed-off-by: Michal Simek <monstr@...str.eu>
> ---
>  arch/microblaze/include/asm/ipc.h       |    1 +
>  arch/microblaze/include/asm/ipcbuf.h    |   36 +++++
>  arch/microblaze/kernel/sys_microblaze.c |  226 +++++++++++++++++++++++++++++++
>  3 files changed, 263 insertions(+), 0 deletions(-)
>  create mode 100644 arch/microblaze/include/asm/ipc.h
>  create mode 100644 arch/microblaze/include/asm/ipcbuf.h
>  create mode 100644 arch/microblaze/kernel/sys_microblaze.c

I don't quite remember what the outcome of this discussion was the last
time, but what is your plan for the deprecated syscalls like the
legacy syscalls you add here?

Have you tried changing uClibc and/or glibc so you don't need them?
Are you planning to remove them soon once they are not needed any
more?

What about the syscalls that are not needed but you just get from
common code (e.g. oldumount, time, old_readdir, ...)?

	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/