From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id X5TwE8fdqmM3CwoAWB0awg (envelope-from ) for ; Tue, 27 Dec 2022 06:57:59 -0500 Received: by simark.ca (Postfix, from userid 112) id 400BE1E222; Tue, 27 Dec 2022 06:57:59 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=lists.lttng.org header.i=@lists.lttng.org header.a=rsa-sha256 header.s=default header.b=xcN/o9PN; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_REPLYTO_END_DIGIT,HTML_MESSAGE, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 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 0BF391E0D3 for ; Tue, 27 Dec 2022 06:57:58 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1672142277; bh=L5mV89GPu5CwmA1d6ErU2UBSdkPyLuHd1+DW98MhO6E=; h=References:In-Reply-To:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=xcN/o9PNMChELAIwiyXMWZMdpH+wjkCGLzhllLxLR/Aw0sc4wKS47adUJYjJcupv5 SNH+l+ocgdliyEEEXo4+JP6J8vApWNgR43I3LnwSrrGLOEyJJkeEYWlaCDmAzKb1HP +S9Mc6RXBajkycKmwf0KRImsmjIzs01jVY8D2Su5WApITfyTSnUwh+a2PqsMgUiBR1 w9PTazsmfQjYTuhFAk7Ga8WK9D5/UUS87ys7LlbOMqsXGzD9D5wK2pbXdRfLFH8EqQ hmtRM3dN2pc/4gKoce6UUsFZThLe/3be2/5ZulaJDtbxCnM+xHFTcFsiMlACKbzYpP cfJ8M7cYV91og== Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4NhCpF3R7Pz1HS7; Tue, 27 Dec 2022 06:57:57 -0500 (EST) Received: from mail-vs1-f43.google.com (mail-vs1-f43.google.com [209.85.217.43]) by lists.lttng.org (Postfix) with ESMTPS id 4NhCpD2MbWz1HS6 for ; Tue, 27 Dec 2022 06:57:56 -0500 (EST) Received: by mail-vs1-f43.google.com with SMTP id a66so12438943vsa.6 for ; Tue, 27 Dec 2022 03:57:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6pzdgW5i4+lrN31aANsx0fC5F+GMTJEHCktVgxRZCSY=; b=EJ+nehbqEJH14S4koSG5yiksLtkuVvlcPasPhrp35TD+re+KSkGVXBg1s2x0K7+CEh UFx1tvh3E5bQL0k3XsTeM23tWsaa5HQUIuz5EXPR4Xqr91sA36F9YH5miX5oQdq+O69X WYmc0BXOBvOcIQfq6DfldXFykh7Q1LOXQdIhTgFc+Amds2bePiDQdtWTvM7Oa4b2JQBK wsDzlrSdfP6vT4iwFMG2YdNwGEZX/9UPPn80ozFVYDxRZcEqnlUS5WarY1XRQJXeNOjZ SPMKhEdKy/6SwkAgOCcJguyufnG4VZ3bQJ2E5eNQ+atzgwTu2rvS11JgZW4sj46W76vl wNqw== X-Gm-Message-State: AFqh2krcbstH1lZRxuhLR6Q0LD2/KN/PeRGYGuVYy82wd85c0+joHNfA RtePvc+tVDwloZX3pl+GN0W8HuePmvT0L6CTT+30hiE4zn+K8w== X-Google-Smtp-Source: AMrXdXuEnIfWPEkme92+68YQwFW687OIYtXiy3JhuyyquuQWJHtVH+wivx6hllr5ZIE+1Ojyyy+0KAXkLF9olVYhdws= X-Received: by 2002:a05:6102:2389:b0:3b1:352b:b22a with SMTP id v9-20020a056102238900b003b1352bb22amr2509064vsr.40.1672142215078; Tue, 27 Dec 2022 03:56:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 27 Dec 2022 17:26:44 +0530 Message-ID: To: lttng-dev@lists.lttng.org Subject: Re: [lttng-dev] Suspected Bug in lttng-tools X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Shubham Kulkarni via lttng-dev Reply-To: Shubham Kulkarni Content-Type: multipart/mixed; boundary="===============2110879733823383622==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============2110879733823383622== Content-Type: multipart/alternative; boundary="000000000000be693b05f0cdf234" --000000000000be693b05f0cdf234 Content-Type: text/plain; charset="UTF-8" Hi, Please ignore the previous mail from me saying there might be a bug in lttng-tools. After some analysis, I found this is expected functionality as per the commit https://github.com/lttng/lttng-tools/commit/cb034ca. It's NOT A BUG. Thanks, Shubham On Mon, Dec 26, 2022 at 3:52 PM Shubham Kulkarni wrote: > Hi, > > I am entirely new to the lttng-tools and frankly not aware of anything. > But, one of our company's customer reported this issue, so I tried > reproducing. I was able to reproduce it with the version of lttng-tool > (2.12.4 - (Ta) Meilleure) installed on my Ubuntu 16.04 ( > https://lttng.org/docs/v2.12/#doc-ubuntu-ppa). > > Issue is, if I try to snapshot a session with an output filename > containing a ".", it fails. Steps I followed are given below : > > *"* > root@MVIN00032:~# lttng create flightrecorder --snapshot > Snapshot session flightrecorder created. > Default snapshot output set to > /home/shubham/lttng-traces/flightrecorder-20221223-153147 > Every channel enabled for this session will be set to mmap output and > default to overwrite mode. > > root@MVIN00032:~# lttng enable-event -k -a > All Kernel events are enabled in channel channel0 > > root@MVIN00032:~# lttng start > Tracing started for session flightrecorder > > root@MVIN00032:~# lttng -vvv snapshot record -s flightrecorder -n > *record.dump* > DEBUG1 - 15:32:15.173476719 [7159/7159]: LSM cmd type : 28 (in > send_session_msg() at lttng-ctl.c:128) > *Error: Create directory failed* > DEBUG1 - 15:32:15.197542565 [7159/7159]: Clean exit (in clean_exit() at > lttng.c:152) > > root@MVIN00032:~# lttng -vvv snapshot record -s flightrecorder -n > *record_dump* > DEBUG1 - 15:32:24.013450964 [7442/7442]: LSM cmd type : 28 (in > send_session_msg() at lttng-ctl.c:128) > *Snapshot recorded successfully for session flightrecorder* > > root@MVIN00032:~# lttng stop > Waiting for data availability > Tracing stopped for session flightrecorder > > root@MVIN00032:~# lttng destroy > Session flightrecorder destroyed *"* > > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > I tried the same with lttng-tools v2.9.5 (as one of my company's product > uses this version) under runqemu session, which worked fine for > 'record.dump' & with lttng-tools v2.11.5 (another product uses this > version) failed with the same error. So, maybe in between these versions an > issue was introduced. > > I am not sure whether this is the correct location to send this mail, but > I didn't find any solution on the Internet and I am not aware of lttng at > all. I was able to reproduce the issue with help from the internet, so > thought to report it via this mailing list. > > Thanks, > Shubham > --000000000000be693b05f0cdf234 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Please ignore the previo= us mail from me saying there might be a bug in lttng-tools. After some anal= ysis, I found this is expected functionality as per the commit=C2=A0https://github.com= /lttng/lttng-tools/commit/cb034ca. It's=C2=A0NOT A BUG.
<= br>
Thanks,
Shubham

On Mon, D= ec 26, 2022 at 3:52 PM Shubham Kulkarni <shubhambkul16@gmail.com> wrote:
Hi,

= I am entirely new to the lttng-tools and frankly not aware of anything. But= , one of our company's customer reported=C2=A0this issue, so I tried re= producing. I was able to reproduce=C2=A0it with the version of lttng-tool (= 2.12.4 - (Ta) Meilleure) installed on my Ubuntu 16.04 (https://lttng.org/do= cs/v2.12/#doc-ubuntu-ppa).

Issue is, if I try = to snapshot a session with an output filename containing a ".", i= t fails. Steps I followed are given below :

&qu= ot;
root@MVIN00032:~# lttng create flightrecorder --snapshot<= br>Snapshot session flightrecorder created.
Default snapshot output set = to /home/shubham/lttng-traces/flightrecorder-20221223-153147
Every chann= el enabled for this session will be set to mmap output and default to overw= rite mode.

root@MVIN00032:~# lttng enable-event -k -a
All Kernel = events are enabled in channel channel0

root@MVIN00032:~# lttng start=
Tracing started for session flightrecorder

root@MVIN00032:~# ltt= ng -vvv snapshot record -s flightrecorder -n=C2=A0record.dump
DEB= UG1 - 15:32:15.173476719 [7159/7159]: LSM cmd type : 28 (in send_session_ms= g() at lttng-ctl.c:128)
Error: Create directory failed
DEBUG1 = - 15:32:15.197542565 [7159/7159]: Clean exit (in clean_exit() at lttng.c:15= 2)

root@MVIN00032:~# lttng -vvv snapshot record -s flightrecorder -n= =C2=A0record_dump
DEBUG1 - 15:32:24.013450964 [7442/7442]: LSM cm= d type : 28 (in send_session_msg() at lttng-ctl.c:128)
Snapshot recor= ded successfully for session flightrecorder

root@MVIN00032:~# lt= tng stop
Waiting for data availability
Tracing stopped for session fl= ightrecorder

root@MVIN00032:~# lttng destroy
Session flightrecord= er destroyed=C2=A0"
-----------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------

I tried the same with=C2=A0lttng-tools v2.9.5 (as one of my company's= product uses this version) under runqemu session, which worked fine for &#= 39;record.dump' & with lttng-tools v2.11.5 (another product uses th= is version) failed with the same error. So, maybe in between=C2=A0these ver= sions an issue was introduced.

I am not sure wheth= er this is the correct location to send this mail, but I didn't find an= y solution on the Internet and I am not aware of lttng at all. I was able t= o reproduce the issue with help from the internet, so thought to report it = via this mailing list.

Thanks,
Shubham
--000000000000be693b05f0cdf234-- --===============2110879733823383622== 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 --===============2110879733823383622==--