From: Greg KH <gregkh@linuxfoundation.org>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: Pavel Skripkin <paskripkin@gmail.com>,
FMDF <fmdefrancesco@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
Date: Mon, 18 Oct 2021 10:48:25 +0200 [thread overview]
Message-ID: <YW002dG2NebAMNlf@kroah.com> (raw)
In-Reply-To: <CAD-N9QW0NEi6Jzh-bu0Bb=RFB6405G28t_jtctk_t8Kw+HUpVQ@mail.gmail.com>
On Mon, Oct 18, 2021 at 04:41:14PM +0800, Dongliang Mu wrote:
> On Mon, Oct 18, 2021 at 4:07 PM FMDF <fmdefrancesco@gmail.com> wrote:
> >
> > On Mon, 18 Oct 2021, 04:46 Dongliang Mu, <mudongliangabcd@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I am writing to kindly ask one question: is there any tracing
> >> mechanism in Linux kernel that can trace all the executed instructions
> >> of a user process? If this user process is run on different
> >> processors, traces of this process on different processors should be
> >> also recorded.
> >
> >
> > You've not explained in detail what is the purpose of the tracing that you want to do. Missing this information I can only provide you a list of links to various tools and methods. Take a look by yourself and try to figure out what is better suited for your needs...
>
> I want to log all the executed instructions of a user process (e.g.,
> poc.c in syzkaller) in the kernel mode and then would like to leverage
> backward analysis to capture the root cause of kernel panic/crash.
>
> Therefore, I need the instruction-level tracing mechanisms or tools.
Then use a userspace debugger like gdb, that is what they are designed
for.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: FMDF <fmdefrancesco@gmail.com>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
Date: Mon, 18 Oct 2021 10:48:25 +0200 [thread overview]
Message-ID: <YW002dG2NebAMNlf@kroah.com> (raw)
In-Reply-To: <CAD-N9QW0NEi6Jzh-bu0Bb=RFB6405G28t_jtctk_t8Kw+HUpVQ@mail.gmail.com>
On Mon, Oct 18, 2021 at 04:41:14PM +0800, Dongliang Mu wrote:
> On Mon, Oct 18, 2021 at 4:07 PM FMDF <fmdefrancesco@gmail.com> wrote:
> >
> > On Mon, 18 Oct 2021, 04:46 Dongliang Mu, <mudongliangabcd@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I am writing to kindly ask one question: is there any tracing
> >> mechanism in Linux kernel that can trace all the executed instructions
> >> of a user process? If this user process is run on different
> >> processors, traces of this process on different processors should be
> >> also recorded.
> >
> >
> > You've not explained in detail what is the purpose of the tracing that you want to do. Missing this information I can only provide you a list of links to various tools and methods. Take a look by yourself and try to figure out what is better suited for your needs...
>
> I want to log all the executed instructions of a user process (e.g.,
> poc.c in syzkaller) in the kernel mode and then would like to leverage
> backward analysis to capture the root cause of kernel panic/crash.
>
> Therefore, I need the instruction-level tracing mechanisms or tools.
Then use a userspace debugger like gdb, that is what they are designed
for.
good luck!
greg k-h
next prev parent reply other threads:[~2021-10-18 8:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 2:45 Any tracing mechanism can track the executed instructions of a user process in the kernel? Dongliang Mu
2021-10-18 2:45 ` Dongliang Mu
2021-10-18 4:09 ` Aruna Hewapathirane
2021-10-18 7:08 ` Pavel Skripkin
2021-10-18 7:08 ` Pavel Skripkin
2021-10-18 8:06 ` FMDF
2021-10-18 8:41 ` Dongliang Mu
2021-10-18 8:41 ` Dongliang Mu
2021-10-18 8:48 ` Greg KH [this message]
2021-10-18 8:48 ` Greg KH
2021-10-18 9:17 ` Dongliang Mu
2021-10-18 9:17 ` Dongliang Mu
2021-10-18 9:48 ` FMDF
2021-10-18 10:12 ` FMDF
2021-10-18 15:10 ` Valdis Klētnieks
2021-10-18 15:10 ` Valdis Klētnieks
2021-10-18 21:00 ` jim.cromie
2021-10-18 21:00 ` jim.cromie
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=YW002dG2NebAMNlf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=fmdefrancesco@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=paskripkin@gmail.com \
/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.