From: chrubis@suse.cz
To: Jessica Foest <jessica.foest@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP syscall question
Date: Mon, 24 Feb 2014 13:37:40 +0100 [thread overview]
Message-ID: <20140224123740.GA23791@rei> (raw)
In-Reply-To: <CAPxN80CzjoOyhTwsPii42+u2qxO=u5oe0B_jok7TozzX-=nNow@mail.gmail.com>
Hi!
> I'm a new user of LTP tool , my goal is to execute some system calls using
> LTP and to intercept them using a kernel tracer .
>
> i do this example :
>
> /opt/ltp/runltp -q -p -l result.03.log -f
> /home/jessica/LTP-test/test-syscall.txt
>
> the content of the test-syscall.txt file is :
> #Tag Test case
> #---------------------------------------
> fork01 fork01
> chdir01 symlink01 -T chdir01
> #----------------------------------------
>
> the problem is that i didn't intercept the syscall fork and the syscall
> chdir using my tracer in the kernel space.
>
> So i wanna ask :
> Which processes are responsible of the execution of these system calls ?
> Does this tool, i mean LTP, really execute these system calls ( fork and
> chdir ) in the kernel space?
The test itself (standalone executable binary) calls the syscall to be
tested. But these are not the only syscalls that the test calls you
cannot write a test that calls a single syscall. You can run most of the
tests directly (without the runltp script) if you execute the cmdline
(marked as Test case in your example file) in the directory with the
test binaries or if you add the path to your PATH.
Moreover the runltp tool that runs LTP tests forks a few times before
the actual test is executed. You cannot run new program without doing
fork() beforehand in UNIX. So in your place, I would double check if the
kernel tracing works.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-02-24 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 0:12 [LTP] LTP syscall question Jessica Foest
2014-02-24 12:37 ` chrubis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140224123740.GA23791@rei \
--to=chrubis@suse.cz \
--cc=jessica.foest@gmail.com \
--cc=ltp-list@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox