linux-kernel - Re: [PATCH] cris: Wire up missing syscalls

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: <201506031523.t53FN6pF006352@ignucius.se.axis.com>
Date:	Wed, 3 Jun 2015 17:23:06 +0200
From:	Hans-Peter Nilsson <hans-peter.nilsson@...s.com>
To:	jespern@...s.com
CC:	xili_gchen_5257@...mail.com, linux-kernel@...r.kernel.org,
	linux-cris-kernel@...s.com
Subject: Re: [PATCH] cris: Wire up missing syscalls

> From: Jesper Nilsson <jespern@...s.com>
> Date: Wed, 3 Jun 2015 17:04:26 +0200

> On Wed, Jun 03, 2015 at 01:36:47PM +0200, Chen Gang wrote:
> >  - For v10, need we also use "sys*" instead of "_sys*"?
> 
> No, the trick here is that v10 and v32 uses different standards
> with regards to prefixing underscore. I'm hoping to fix that someday.

Not exactly, but almost; please let me fill in JFTR:

Most people probably guessed correctly that this is related to
building the CRIS v10 kernel with the *-elf toolchain (which has
the convention that symbols are prefixed with underscores for
cris-*-elf and crisv32-*-elf) while (IIUC) the CRIS v32 kernel
is built with the *-linux-gnu toolchain (which does not have any
symbol prefix for cris-*-linux-gnu crisv32-*-linux-gnu).

One Might Imagine that there'd be build machinery in place in
the kernel such that such a symbol prefix issue could be hidden,
like a header to include and using e.g. S(symbol) in all
assembly files.  (Actually some time ago I thought there already
was, but Jesper corrected me.)

brgds, H-P
--
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/