lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Mohammad Kavousi via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: Yan Chen <ychen@northwestern.edu>,
	Xutong Chen <XutongChen2021@u.northwestern.edu>
Subject: [lttng-dev] LTTng Support for Network Namespace
Date: Mon, 8 Feb 2021 12:04:53 -0600	[thread overview]
Message-ID: <CAK7B4KcwnAK_u5t-F_ujjeG=mnEXBAtr4PfdcHuhqccrRmbo_Q@mail.gmail.com> (raw)


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

Dear LTTng developers,

I was wondering if LTTng currently (or in the future) supports network
namespaces. For instance, an ambiguity in the logs would make problems for
future system analysis.

Taking the "bind" system call, that would help us distinguish between
different local IP addresses when two or more container instances are
running on the host, given that the "umyaddr" field is an address inside
the memory, how would we recover the local addresses after the trace has
been collected?

syscall_entry_bind: { cpu_id = 1 }, { mnt_ns = 4026532553, pid = 532, tid =
532, vtid = 532, vpid = 532 }, { fd = 14, umyaddr = 93827759199256, addrlen
= 12 }


Thanks, we appreciate the help beforehand!


Mohammad

[-- Attachment #1.2: Type: text/html, Size: 1154 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-02-08 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 18:04 Mohammad Kavousi via lttng-dev [this message]
2021-02-08 19:38 ` [lttng-dev] LTTng Support for Network Namespace Mathieu Desnoyers 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='CAK7B4KcwnAK_u5t-F_ujjeG=mnEXBAtr4PfdcHuhqccrRmbo_Q@mail.gmail.com' \
    --to=lttng-dev@lists.lttng.org \
    --cc=XutongChen2021@u.northwestern.edu \
    --cc=kavousi@u.northwestern.edu \
    --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).