From: Karel Zak <kzak@redhat.com>
To: Harald Hoyer <harald@redhat.com>
Cc: linux-kernel@vger.kernel.org, power@bughost.org
Subject: Re: [PATCH] tracer for sys_open() - sreadahead
Date: Mon, 9 Feb 2009 14:13:54 +0100 [thread overview]
Message-ID: <20090209131354.GC3205@nb.net.home> (raw)
In-Reply-To: <gmeu0q$n13$1@ger.gmane.org>
On Thu, Feb 05, 2009 at 03:44:42PM +0100, Harald Hoyer wrote:
> Ingo Molnar wrote:
>> * Pavel Machek <pavel@suse.cz> wrote:
>>
>>> On Tue 2009-01-27 12:08:04, Kok, Auke wrote:
>>>> This tracer monitors regular file open() syscalls. This is a fast
>>>> and low-overhead alternative to strace, and does not allow or
>>>> require to be attached to every process.
>>>>
>>>> The tracer only logs succesfull calls, as those are the only ones we
>>>> are currently interested in, and we can determine the absolute path
>>>> of these files as we log.
>>> Maybe fanotify() should be used instead?
>>>
>>> Or maybe just plain strace? One slow boot should not really hurt...
>>
>> ptrace is out of question for good tracing because it's not a
>> transparent probe. (ptrace monopolizes the traced task - if we use that
>> then we break regular strace usage.)
>>
>> Ingo
>
> Can strace can be used on init?
>
> $ man strace
> ...
> On Linux, exciting as it would be, tracing the init process is forbidden.
> ...
>
> Any hope getting _any_ mechanism in the kernel??
Do you remember Linux Auditing System? That's RH's baby with hooks to
all relevant syscalls. It would be better to fix/improve the current
kernel mechanisms that introduce a new one.
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2009-02-09 13:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 20:08 [PATCH] tracer for sys_open() - sreadahead Kok, Auke
2009-01-27 20:51 ` Arnaldo Carvalho de Melo
2009-01-27 21:14 ` Frederic Weisbecker
2009-01-28 22:05 ` Kok, Auke
2009-01-29 0:45 ` Arnaldo Carvalho de Melo
2009-01-29 13:39 ` Frédéric Weisbecker
2009-01-29 13:40 ` Frédéric Weisbecker
2009-01-27 22:43 ` Frederic Weisbecker
2009-01-27 22:50 ` Frederic Weisbecker
2009-01-29 14:04 ` Ingo Molnar
2009-01-29 14:29 ` Frédéric Weisbecker
2009-01-29 14:31 ` Ingo Molnar
2009-01-29 14:40 ` Frédéric Weisbecker
2009-01-29 14:48 ` Frédéric Weisbecker
2009-01-29 15:09 ` Ingo Molnar
2009-01-29 15:17 ` Frédéric Weisbecker
2009-01-29 15:34 ` Frédéric Weisbecker
2009-01-29 15:53 ` Frank Ch. Eigler
2009-01-28 0:43 ` Frank Ch. Eigler
2009-01-28 13:58 ` Frédéric Weisbecker
2009-01-28 14:29 ` Arnaldo Carvalho de Melo
2009-01-28 9:38 ` Ananth N Mavinakayanahalli
2009-01-28 14:21 ` Frédéric Weisbecker
2009-01-28 17:00 ` Ananth N Mavinakayanahalli
2009-01-28 17:15 ` Frédéric Weisbecker
2009-01-28 22:19 ` Kok, Auke
2009-01-30 20:22 ` Pavel Machek
2009-02-03 13:32 ` Ingo Molnar
2009-02-05 14:44 ` Harald Hoyer
2009-02-05 15:07 ` Bill Nottingham
2009-02-05 15:14 ` Arjan van de Ven
2009-02-05 15:24 ` Bill Nottingham
2009-02-05 15:47 ` Arjan van de Ven
2009-02-06 23:18 ` Corrado Zoccolo
2009-02-09 13:13 ` Karel Zak [this message]
2009-02-09 13:23 ` Harald Hoyer
2009-02-09 13:54 ` Karel Zak
2009-02-11 10:44 ` Harald Hoyer
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=20090209131354.GC3205@nb.net.home \
--to=kzak@redhat.com \
--cc=harald@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=power@bughost.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.