lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Mohammad Kavousi <kavousi@u.northwestern.edu>, lttng-dev@lists.lttng.org
Cc: Yan Chen <ychen@northwestern.edu>,
	Xutong Chen <XutongChen2021@u.northwestern.edu>
Subject: Re: [lttng-dev] LTTng Support for Mount Namespace
Date: Wed, 6 Jan 2021 12:02:00 -0500	[thread overview]
Message-ID: <977d5fa1-ff33-f99e-5be9-7c53ff6adfc4@efficios.com> (raw)
In-Reply-To: <CAK7B4KePHyJFCwAczqcqz+05Ts8AVm0Xh9f4hwSBKaVhQLz8cw@mail.gmail.com>

On 2021-01-06 10 h 50, Mohammad Kavousi via lttng-dev wrote:
> Dear LTTng developers,
> 
> Our group at Northwestern has been using your amazing tool for the 
> purpose of provenance tracking on Linux-based systems and we are very 
> fond of the performance and accuracy it provides.
> 
> Our analysis shows that mnt_ns context is supported in the 2.12 version 
> of LTTng. However, though, adding the mnt_ns context using 
> the add-context command produces this error:
> 
> Error: mnt_ns: Context unavailable on this kernel
> 
> We have tried adding the context to the more recent version of the 
> kernel (5.8) on Ubuntu 20.04, as well as older kernel versions such as 
> the 4.4 version on Ubuntu 16.04. However, we always receive the above 
> error trying to add the mnt_ns context.
> 
> We could not find which kernel versions are supported for adding this 
> context, or whether they need to be built with special flags. I would 
> appreciate your guidance on resolving this issue.
> 
> 
> Thank you,
> Mohammad

Hi,

Unfortunately the definition of 'struct mnt_namespace' is in a private 
kernel header (fs/mount.h) unlike other namespaces.  Private headers are 
not included in the kernel headers package of distributions like Ubuntu, 
to build support for this namespace context in lttng-modules you need to 
use the full kernel source tree.

Or as a quick hack, you could copy 'fs/mount.h' from the original source 
tree to your kernel headers package build directory, which on Ubuntu is 
usually '/lib/modules/$(uname -r)/build'.

Hoe this helps,

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

  reply	other threads:[~2021-01-06 17:02 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 [this message]
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
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=977d5fa1-ff33-f99e-5be9-7c53ff6adfc4@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;
as well as URLs for NNTP newsgroup(s).