linux-kernel - Re: where is the code for read system call?

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

Message-Id: <20070723093520.16f97256.randy.dunlap@oracle.com>
Date:	Mon, 23 Jul 2007 09:35:20 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Karsten Wiese <fzu@...gehoertderstaat.de>
Cc:	"Agarwal, Lomesh" <lomesh.agarwal@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: where is the code for read system call?

On Mon, 23 Jul 2007 18:01:32 +0200 Karsten Wiese wrote:

> Am Montag, 23. Juli 2007 schrieb Agarwal, Lomesh:
> > For future how do I trace a system call to a function in a kernel?
> 
> strace. i.e:
> 	$ strace ls

I thought (maybe I misunderstood) that Lomesh wanted to know
which kernel function (by name) is called for specific syscalls...
and strace will tell the syscall by name, but not the kernel
function names.

If Lomesh wants what I described, then the answer is more like
"see the syscall tables in each $ARCH".

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/