From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BE8ED286D69; Thu, 28 Aug 2025 20:51:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756414304; cv=none; b=NxSujv9GrzaqP/2CJj0lEhETjkeq5R08FLeNSPH3xZjDNRX/1Ebeqzm3t1+qz4APbUK51kU5rHjkvY5wOwKcuIScevJ7Ke+ZDHPARSF3Wei0fTG3hy/8uObd+vGQPQw2Z5tDZJ8BBT7UQQZAWKcuSombKaubnE4XxH4q+L0j58g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756414304; c=relaxed/simple; bh=FxH/pDnOssLoWeo5YWzH6Hmb4odFQlWNIVnuiWhowJY=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=QoczENwMBKOsK5SO+sineGJtCih5JRtOQ/dBcqJJIfpqqAKJ39rMnJiKH1RnzVzJW1zMX2Foy0YwcQAxSU6qjSaojat/Q8L2+uI9gf4nN6VkkPGJTOjkg+m6ihENh0Q+BxMw2Y51jcREh47JYIeEDlaj2jHPKME9h1xulNQCS8Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=GmxGqgFr; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="GmxGqgFr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A85EEC4CEEB; Thu, 28 Aug 2025 20:51:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1756414304; bh=FxH/pDnOssLoWeo5YWzH6Hmb4odFQlWNIVnuiWhowJY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GmxGqgFryDHYc//IDjodBcWsQvNgkmjwd/lgo2PrvKO9PiXgFbEN6It8ETfcCYsXw NU51DFZ1nnVyh5DB0A5tFSH6yvXBdfQ2Zm79NuLMtzYhOIWzddrwJKcwulCQM2wmma n2G5GP+r4wGCACqxsgtecMmyCPXHaioUUtFChXLDK2fgM/aHwbq3An+RT66WZASVXa Hb3Jj+WmwjgXhIxynm5lEmouFDf8SlOrSi5sz3TqnzAmaRlfVznD/PPR0a9D+N8/yO 1thagHK7hWIpLkZ8dc/zmmVHNozxCAHlLVjKihyExVeCLv7yudGg7VXUFRCszrqaAu C6zn1d1UPd5Mg== Date: Thu, 28 Aug 2025 16:51:39 -0400 From: Steven Rostedt To: Arnaldo Carvalho de Melo Cc: Linus Torvalds , linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org, x86@kernel.org, Masami Hiramatsu , Mathieu Desnoyers , Josh Poimboeuf , Peter Zijlstra , Ingo Molnar , Jiri Olsa , Arnaldo Carvalho de Melo , Namhyung Kim , Thomas Gleixner , Andrii Nakryiko , Indu Bhagat , "Jose E. Marchesi" , Beau Belgrave , Jens Remus , Andrew Morton , Florian Weimer , Sam James , Kees Cook , Carlos O'Donell Subject: Re: [PATCH v6 5/6] tracing: Show inode and device major:minor in deferred user space stacktrace Message-ID: <20250828165139.15a74511@batman.local.home> In-Reply-To: <583E1D73-CED9-4526-A1DE-C65567EA779D@gmail.com> References: <20250828180300.591225320@kernel.org> <20250828180357.223298134@kernel.org> <20250828161718.77cb6e61@batman.local.home> <583E1D73-CED9-4526-A1DE-C65567EA779D@gmail.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-trace-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 28 Aug 2025 17:27:37 -0300 Arnaldo Carvalho de Melo wrote: > >I would love to have a hash to use. The next patch does the mapping > >of the inode numbers to their path name. It can > > The path name is a nice to have detail, but a content based hash is > what we want, no? > > Tracing/profiling has to be about contents of files later used for > analysis, and filenames provide no guarantee about that. I could add the build id to the inode_cache as well (which I'll rename to file_cache). Thus, the user stack trace will just have the offset and a hash value that will be match the output of the file_cache event which will have the path name and a build id (if one exists). Would that work? -- Steve