From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id YTeXL/vp9V9jbgAAWB0awg (envelope-from ) for ; Wed, 06 Jan 2021 11:48:59 -0500 Received: by simark.ca (Postfix, from userid 112) id B97EA1E940; Wed, 6 Jan 2021 11:48:59 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 21FC41E590 for ; Wed, 6 Jan 2021 11:48:59 -0500 (EST) Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4D9wLL3RgvzNWc; Wed, 6 Jan 2021 11:48:58 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1609951739; bh=va//bRw0cNnSP15jdJmFAvh35jWCIdRa3THvQpkp7GQ=; h=Date:To:Cc:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=x4RBudK0a6f+7rn0aLPUXpusBkIvshG+2r6/ce4d72SRL5Qg8SQMpdlVnn+AEIGUc QYqo8RWsDmkO60K/55mOnuC0InfDr18JQgtqZ81nkvAz4MYTQVjIlh200/56SCmQ8U aQ49QII02//dlCeCC8gtZDKkMlXqV+6/q/p78VDzjJHjLPPJlAXZr/HTbATd8oo37a /8ZW7BZLap0kbfVSs65fXSMdpoXGfnRfqwhS/XKAHL8uuWFhEA27h4qpCrOuhnP5Bb g6sovheLEM9FgflRxPHX2GyaNRQMC5ylxOzCO6TBT+A7UTyjt0JDf7Dl1bzArQ+ObS SvswYwvlrNOyQ== Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) by lists.lttng.org (Postfix) with ESMTPS id 4D9v3k6nwXzNl7 for ; Wed, 6 Jan 2021 10:51:14 -0500 (EST) Received: by mail-lf1-x132.google.com with SMTP id x20so7456604lfe.12 for ; Wed, 06 Jan 2021 07:51:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Hefw/415Lg03T99a3pZ1SsBsH/0UMMfmrstdBiKyFpY=; b=QoTZgCqeGkXZKrKp1dsRsVZBSIH9NLb28d/sD/Sp8VnBf+IrH9jffunx39cd13lwO9 h5InDMhhLKIXY9uJbTv2kEw/6hbgSA2Bq1WmUpbtOKCBuIDIXOfMdF1275ZNwbhSDTfp uJnfwS4ee4TdnlVNFYQhqWVH11FZrt/Fu1vZ2bJ9dOSi0QAQWgLfY9bBMqV1j/QKPaMS 9E0Jwe30kKxmTHtpN/F1V/fhJRPjcpCVGg+xy2fUTyNoo6YppW4IlnSsJWvNJC9FOBni /4oimLLLLNUZ5hhM50F6yUo8fnV4iZcxABAU0ZPWP/XpaGFIjBifcXGM7etZn9MQwrFX /NXQ== X-Gm-Message-State: AOAM530955tg8/czHDv90YU1dAUIxV9HCahwNu4wTidFcfNJ/IzxRbL3 J4e7fSCGNLSbc1rQoMqZukOjJD2BzNe8t+j9rmWOL8DoAYptQg== X-Google-Smtp-Source: ABdhPJxvFdtKhIw8AGzWs8opbl1oJoBmSGj/ihAH9/gYIqvRNg+49dCeiX/Urc9M8jrQ6LUFcZibWZ+vKBOIBVdn5rU= X-Received: by 2002:a19:40d6:: with SMTP id n205mr2051174lfa.24.1609948273115; Wed, 06 Jan 2021 07:51:13 -0800 (PST) MIME-Version: 1.0 Date: Wed, 6 Jan 2021 09:50:36 -0600 Message-ID: To: lttng-dev@lists.lttng.org Cc: Yan Chen , Xutong Chen X-Mailman-Approved-At: Wed, 06 Jan 2021 11:48:57 -0500 Subject: [lttng-dev] LTTng Support for Mount Namespace X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.31 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Mohammad Kavousi via lttng-dev Reply-To: Mohammad Kavousi Content-Type: multipart/mixed; boundary="===============3791180039674183041==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============3791180039674183041== Content-Type: multipart/alternative; boundary="000000000000ed1bae05b83d4a2d" --000000000000ed1bae05b83d4a2d Content-Type: text/plain; charset="UTF-8" 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 --000000000000ed1bae05b83d4a2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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. Howev= er, though, adding the mnt_ns context using the=C2= =A0add-context command produces thi= s error:

Error: mnt_ns: Context unavailable on this k= ernel

We have tried adding the context to= the more recent version of the kernel (5.8) on Ubuntu 20.04, as well as ol= der kernel versions such as the 4.4 version on Ubuntu 16.04. However, we al= ways 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 y= ou,
Mohammad
=


--000000000000ed1bae05b83d4a2d-- --===============3791180039674183041== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============3791180039674183041==--