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: <8bd0f97a0912101317v8143e67w9e2f1224111ac0d7@mail.gmail.com>
Date:	Thu, 10 Dec 2009 16:17:44 -0500
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	liqin.chen@...plusct.com, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: What's in asm-generic.git

2009/12/10 Arnd Bergmann:
> On Monday 07 December 2009, Arnd Bergmann wrote:
>> On Monday 07 December 2009, liqin.chen@...plusct.com wrote:
>> > Arnd Bergmann <arnd@...db.de> 写于 2009-12-04 03:14:08:
>> >
>> > Maybe you can add a __NR_set_thread_area define in asm-generic/unsitd.h
>> > for tls used.
>>
>> Yes, good point. I'll update the syscall list with this, and also check if more
>> syscalls have been addded.
>
> I have found now that sys_accept4 was missing. sys_set_thread_area however
> is only defined on x86 and mips. Since you don't currently implement this
> on score, maybe it would be more appropriate to handle it like the other
> architectures do, rather than adding it to asm-generic/unistd.h?

isnt the point of asm-generic/unistd.h to collect all common syscalls
?  if there's syscalls that ideally should be handled by everyone but
currently doesnt, then it's easy to define it in the header but have
the actual entry.S leave it as a hole ...

or maybe i'm missing what's going on
-mike
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ