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 B7F3E10F1 for ; Tue, 31 Dec 2024 14:09:14 +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=1735654155; cv=none; b=Yxxg/UGx+fNQ/ZMIEspURI6renqUDIsQz5B/9SSGpuDc2ESFXJ/1C8JZrFebnv8aHt+cGYQAOO0KaI6YRD58f9N28PtQBJ4PbepFQq2aYoSsIslIgCbpF6652OQLOIRdEgzEt2UxDC5txo4wdN9XGk9VEnx96vG2VpPgamEMQB8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735654155; c=relaxed/simple; bh=IRi28iCj07EWDw82lOWDebDHcks06FIs37QkNH56q/I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=eRWMl++Y5j9tfUEDgGPZteBBJQc21RHCJlghaK1CLJUEhirD6JHsOWbypPid5ZlqjP3Tmh4Au/PbZJTU6KiLBvii4VqQAefJHwCKcuy3tr0MFo3G87TdovQk29e2siZmtqBL8RtWLqOP1lZV5LYrrUflm5O2VA0YOQwMbkunfyY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=sCcRbxek; 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="sCcRbxek" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 11697C4CED2; Tue, 31 Dec 2024 14:09:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1735654154; bh=IRi28iCj07EWDw82lOWDebDHcks06FIs37QkNH56q/I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sCcRbxekVhkdK2bh3un4lfgTWDC5HIggv5ikzsV3CEEEsUYDSacRPhv74a6vKyOYB pZWvU/J37BWpCNyXW8ubWpqggpUqoB40AuL6midDa6OUnPhSWo3WTDL3OPJzeMO6iE zdLmR6GfA47PAvakgLoxwivHSU5ftPKFBqNkkR8+94Dg8cwhVotFDnxbHtTjutUNQU eg9APHPLpj6hru3oZv9eboqbMF/taAK74CILOkCTu4iVotIT/bAcl8QlEiEkeg8x51 2zul/59jRYn80SBpi3IxNHfQyYVcEPqm+3ct0bYYptl4RtlpIKrAO1DcyC7smaJWpS MOEEiXJbdnPbQ== Date: Tue, 31 Dec 2024 09:09:12 -0500 From: Sasha Levin To: Steven Rostedt Cc: Linus Torvalds , LKML , Masami Hiramatsu , Mathieu Desnoyers , Gene C Subject: Re: [GIT PULL] tracing: Fix trace event check for 6.13 Message-ID: References: <20241231085622.35f69353@gandalf.local.home> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20241231085622.35f69353@gandalf.local.home> On Tue, Dec 31, 2024 at 08:56:22AM -0500, Steven Rostedt wrote: > >Linus, > >Tracing fix for 6.13: > >- Fix trace event string check when dealing with array of strings > > The xe_bo_move event has a field that indexes into an array of > strings. The TP_fast_assign() added the index into the ring buffer > and the TP_printk() had a "%s" that referenced the array using the > index in the ring buffer. This is a legitimate use of "%s" in > trace events. But this triggered a false positive in the > test_event_printk() at boot saying that the string was dangerous. > > Change the check to allow arrays using fields in the ring buffer > as an index to be considered a safe string. > > >Please pull the latest trace-v6.13-rc5 tree, which can be found at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git >trace-v6.13-rc5 You might have forgotten to push the tag :) -- Thanks, Sasha