lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Mohammad Kavousi via lttng-dev <lttng-dev@lists.lttng.org>
To: Michael Jeanson <mjeanson@efficios.com>
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 11:29:29 -0600	[thread overview]
Message-ID: <CAK7B4Kc9bED7q9_6HsCqLT1dhJEjjNY93cspZ7Nb_Ztpn+=ERg@mail.gmail.com> (raw)
In-Reply-To: <f13d262c-560a-849e-c3f2-0c0d6e67e27b@efficios.com>


[-- Attachment #1.1: Type: text/plain, Size: 1476 bytes --]

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

- Run sudo dkms autoinstall (I also did reboot)

- Create the session and attempt to add the context

However, I'm getting the same error.

On Tue, Jan 12, 2021 at 9:05 AM Michael Jeanson <mjeanson@efficios.com>
wrote:

> On 2021-01-09 09 h 03, Mohammad Kavousi wrote:
> > Michael,
> >
> > Thank you for your swift response. However, for the first part, I'm not
> > sure what it means by "using" the full kernel source. How would I use it
> > with lttng-modules?
> >
> > As for the quick hack part, I grabbed the kernel source and copied the
> > mount.h onto the folder you mentioned, and it did not help. I don't
> > expect lttng to automatically find that file and use it; also there are
> > no other header files in the package build directory. Could you kindly
> > give us more instructions?
> >
> > Thanks,
> > Mohammad
>
> The lttng modules are shipped in Ubuntu as a dkms package which means
> they are built directly on your machine for each kernel version you
> install. So after adding the required file in your headers you'll need
> to rebuild the modules with dkms and unload / reload them in your
> running kernel or just reboot the machine.
>
> To rebuild all installed dkms modules for the current kernel:
>
>    sudo dkms autoinstall
>

[-- Attachment #1.2: Type: text/html, Size: 2110 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2021-01-12 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 15:50 [lttng-dev] LTTng Support for Mount Namespace 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 [this message]
2021-01-12 18:51         ` Michael Jeanson via lttng-dev
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='CAK7B4Kc9bED7q9_6HsCqLT1dhJEjjNY93cspZ7Nb_Ztpn+=ERg@mail.gmail.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;
as well as URLs for NNTP newsgroup(s).