linux-kernel - Re: [RFC] Introduce __ARCH_WANT_SYS

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, 23 Apr 2008 23:16:25 +0200
From:	Michal Simek <monstr@...nam.cz>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Will Newton <will.newton@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, git@...inx.com,
	microblaze-uclinux@...e.uq.edu.au
Subject: Re: [RFC] Introduce __ARCH_WANT_SYS_SYSFS

Hi Arnd and others,

I would like to fix syscalls in Microblaze repo. Can you give me a hint how to
do it?

I look at Blackfin arch and I compared files with microblaze. There are some
differences but not so much.
Can you tell me how to test it which syscall is necessary for platform.
I have never found any documentation about.

In my syscall_table.S (on some arch in entry.S) is one big jump table with
reference to syscalls. In unistd.h is definition.

Is there any convention which syscalls are use for all archs and which are
architecture specific?

Thanks for info,
Michal Simek

>> This patch introduces a __ARCH_WANT_SYS_SYSFS #define for
>> architectures that support the sysfs(2) system call. At the moment
>> that's everybody but blackfin, but future architectures may want to
>> save the (admittedly small) code size that it adds to the kernel as
>> well.
> 
> Yes, good thing to have. Since we'll be getting a new architecture
> (microblaze) soon, I think we should extend this mechanism (even though
> it's ugly) to all syscalls that we don't want to have in new architectures
> and make sure that microblaze doesn't have to set any of them.
> 
> 	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/