From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ZB+HF7+krWNvkAsAWB0awg (envelope-from ) for ; Thu, 29 Dec 2022 09:31:27 -0500 Received: by simark.ca (Postfix, from userid 112) id 51E1D1E222; Thu, 29 Dec 2022 09:31:27 -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=EmQ0XV/k; 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 8E8D81E0D3 for ; Thu, 29 Dec 2022 09:31:25 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1672324285; bh=1fUmPVexb0lXJUFGdNkJtgsPp1sY10kaM2CZE5DbUck=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=EmQ0XV/kn7VOal3pbFNv77uYeMcouJdzA2uBreXNCvtiiUp0eDZ5kp4s0tjsE/vVQ Atw2hUZtyv+fUZN0xoQ+fbu/wFZymhR7XsPTe/je8sH9w7vA4zYswwfPMqwyb7ZzBR CxjaLlIqXuOHjzYo6BnjkJEHD/aV/FT6wawyZPrskITl+xAUhmXDsM85Og9eOz9XGe eWh0OfCQh2pHdxDCEdESGLV5emaaKDPspQj63uHdHtwjG1NGf0BPGvS/CkYCDBSitI bZr//p/dInb35/tYcmSPgE21dy8SzKUdKWl+2XR5/73Kfi+GoWh5ZtS6EjZZJgXl/j IKEoZPlWVSz3Q== Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4NjW6N6Fr9z1JSs; Thu, 29 Dec 2022 09:31:24 -0500 (EST) Received: from mail-ed1-f48.google.com (mail-ed1-f48.google.com [209.85.208.48]) by lists.lttng.org (Postfix) with ESMTPS id 4NdnxD3rgNz1GH6 for ; Fri, 23 Dec 2022 08:25:26 -0500 (EST) Received: by mail-ed1-f48.google.com with SMTP id r26so1881629edc.5 for ; Fri, 23 Dec 2022 05:25:26 -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:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=hE+Jpdi/sO0YTo2wm/QmLXB9PcZGXpoEg4iNGKv39Gk=; b=bfa4kslsiA58p2YfNjFi5nWP11JHPSdfcfgu19haJDmOxM+OSoYWFrhlUEZkb5Q3UG iUQ4DI3By72WAT4RHdar+9DPOE/ug4yAhyr2S4dCG28rmty7BQ1IUiO2M4rF+o/mdfew PBqW9gyr+GChTpotOsRDEeXhq5y97G/rzdL2B6BqdTlGs7C7kFeOzHdhgp/xVgLFB98P yHFvnnvlvKGfl47jmLyMK68++2SeHe5X9tuPLSWm7HXqCnC3syvycaxTsdvTX1/tjGaJ I5+h0DyKbIhN6BGB+/ovvnVtczqeXCCJTOTRaq/s+p2djuGvf3qiPseIGKOB3tYXVZlO FODw== X-Gm-Message-State: AFqh2kpqj0XCL7I5MvuitTFc34k6g+C1V1/awjwbmyZSqPfKfzkMdqHq LJlIED1rZOVrCmBcyfNfCHVH+6VeZIENoBongl13PAqzvNcZeA== X-Google-Smtp-Source: AMrXdXvuoYWTwLrBMTaAch07ts8QzxKl9i2yfyF9T0Cf9WtJUu6d6gR7SievmrcMie6gZZ4wgcKEjuD3946xnVlna/o= X-Received: by 2002:a05:6402:481:b0:47f:f170:9b17 with SMTP id k1-20020a056402048100b0047ff1709b17mr400369edv.354.1671801864473; Fri, 23 Dec 2022 05:24:24 -0800 (PST) MIME-Version: 1.0 Date: Fri, 23 Dec 2022 18:54:12 +0530 Message-ID: To: lttng-dev@lists.lttng.org X-Mailman-Approved-At: Thu, 29 Dec 2022 09:31:23 -0500 Subject: [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="===============0387037401866255415==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============0387037401866255415== Content-Type: multipart/alternative; boundary="0000000000004451f905f07eb4a6" --0000000000004451f905f07eb4a6 Content-Type: text/plain; charset="UTF-8" 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 --0000000000004451f905f07eb4a6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I am entirely new to the lttng-tool= s and frankly not aware of anything. But, one of our company's customer= reported=C2=A0this issue, so I tried reproducing. 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/docs/v2.12/#doc-ubuntu-ppa).

<= div>Issue is, if I try to snapshot a session with an output filename contai= ning a ".", it fails. Steps I followed are given below :

"
root@MVIN00032:~# lttng create fli= ghtrecorder --snapshot
Snapshot session flightrecorder created.
Defau= lt snapshot output set to /home/shubham/lttng-traces/flightrecorder-2022122= 3-153147
Every channel enabled for this session will be set to mmap outp= ut and default to overwrite mode.

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

root@M= VIN00032:~# lttng start
Tracing started for session flightrecorder
root@MVIN00032:~# lttng -vvv snapshot record -s flightrecorder -n reco= rd.dump
DEBUG1 - 15:32:15.173476719 [7159/7159]: LSM cmd type : 28 (= in send_session_msg() at lttng-ctl.c:128)
Error: Create directory fai= led
DEBUG1 - 15:32:15.197542565 [7159/7159]: Clean exit (in clean_ex= it() 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)
S= napshot recorded successfully for session flightrecorder

root@MV= IN00032:~# lttng stop
Waiting for data availability
Tracing stopped f= or session flightrecorder

root@MVIN00032:~# lttng destroy
Sessio= n flightrecorder destroyed "
--------------------= ---------------------------------------------------------------------------= ------------------------------------------------------------

=
I tried the same with=C2=A0lttng-tools v2.9.5 (as one of my comp= any's product uses this version) under runqemu session, which worked fi= ne for 'record.dump' & with lttng-tools v2.11.5 (another produc= t uses this version) failed with the same error. So, maybe in between=C2=A0= these versions an issue was introduced.

I am not s= ure 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 w= as able to reproduce the issue with help from the internet, so thought to r= eport it via this mailing list.

Thanks,
= Shubham

--0000000000004451f905f07eb4a6-- --===============0387037401866255415== 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 --===============0387037401866255415==--