linux-kernel - Re: Question: removal of syscall macros?

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: <1166039179.27217.883.camel@laptopd505.fenrus.org>
Date:	Wed, 13 Dec 2006 20:46:19 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Teunis Peters <teunis@...tersgift.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Question: removal of syscall macros?

On Wed, 2006-12-13 at 10:51 -0800, Teunis Peters wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Now that syscall macros have been pulled from the -mm tree, what method
> is recommended to use syscalls?
> 
> (I've wasted a day grubbing through sources before giving up and copying
> the old syscall macros into one key driver)
> 
> _syscall macros are used by:
> ATI driver  (no choice.  I'm working with laptops)

.. which uses it to call mprotect() from inside the driver. That's a
nice security hole right there... better ask ATI to fix it urgently :)

-
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/