From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Mohammad Kavousi <kavousi@u.northwestern.edu>
Cc: lttng-dev@lists.lttng.org, Yan Chen <ychen@northwestern.edu>,
Xutong Chen <XutongChen2021@u.northwestern.edu>
Subject: Re: [lttng-dev] LTTng Support for Mount Namespace
Date: Tue, 12 Jan 2021 13:51:23 -0500 [thread overview]
Message-ID: <869ac606-375e-b15c-9eec-6501865b5c52@efficios.com> (raw)
In-Reply-To: <CAK7B4Kc9bED7q9_6HsCqLT1dhJEjjNY93cspZ7Nb_Ztpn+=ERg@mail.gmail.com>
On 2021-01-12 12 h 29, Mohammad Kavousi wrote:
> Thanks again for your reply,
>
> To be specific, I did exactly this:
>
> - Install linux source code, then copy the mentioned file to the folder
> using: cp
> /usr/src/linux-headers-5.4.0-59/fs/mount.h /lib/modules/$(uname -r)/build
The path to the header has to stay the same, so you would need to copy
it to '/lib/modules/$(uname -r)/build/fs'.
The rest of the steps seem fine.
One thing you can do if it still doesn't work, is modify 'Makefile' and
'Kbuild.common' in the lttng-modules source directory and remove the
conditions on 'mnt_ns_dep'. That would make the build fail when
'fs/mount.h' isn't found and may help you find the cause.
>
> - Run sudo dkms autoinstall (I also did reboot)
>
> - Create the session and attempt to add the context
>
> However, I'm getting the same error.
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2021-01-12 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:50 Mohammad Kavousi via lttng-dev
2021-01-06 17:02 ` Michael Jeanson via lttng-dev
2021-01-09 14:03 ` Mohammad Kavousi via lttng-dev
2021-01-12 15:05 ` Michael Jeanson via lttng-dev
2021-01-12 17:29 ` Mohammad Kavousi via lttng-dev
2021-01-12 18:51 ` Michael Jeanson via lttng-dev [this message]
2021-01-12 20:30 ` Mohammad Kavousi via lttng-dev
2021-01-18 18:18 ` Michael Jeanson via lttng-dev
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=869ac606-375e-b15c-9eec-6501865b5c52@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=XutongChen2021@u.northwestern.edu \
--cc=kavousi@u.northwestern.edu \
--cc=mjeanson@efficios.com \
--cc=ychen@northwestern.edu \
/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