linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Wed, 13 Dec 2006 10:51:05 -0800
From:	Teunis Peters <teunis@...tersgift.com>
To:	linux-kernel@...r.kernel.org
Subject: Question: removal of syscall macros?

-----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)
vmware  (I'm trying to phase this out for qemu, but it's a slow process)
(and others I suspect)

I realize that these are "closed source" but my work is rather dependant
on them remaining operational - and as the 2.6.19 kernel series is the
only one that works on most of the hardware provided by my workplace,
I'm kind of stuck patching things myself.

There doesn't seem to be any documentation on this so I ask about how to
replace the _syscallX calls.

Thank you!
	- Teunis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFgEuYbFT/SAfwLKMRAqYoAJ4xiJGcoJ6EB6kKX1VGALib1NrQyQCeNUzv
AgYtPKfC6SpwBY6PgyLbZeI=
=jN5z
-----END PGP SIGNATURE-----
-
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/