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 3DC1C3A9DAB for ; Mon, 20 Apr 2026 18:10:36 +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=1776708636; cv=none; b=XKWpD+i7n3ZaNN6lO/iqJJnoginRZLHQyZ3ViX6NGDaaOh3A1xu4l+zNOhi/CV33dy14KIWpbWZrlSgCHaUdF7YLR1CL0mbwAVEkkgl2x58cUv6MmYkghce0KiU05XNHC88vKz14C1SYwYG7DxUOiZG9xLqfsciS2/MC5YCIOdM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776708636; c=relaxed/simple; bh=WM5JLDywrrTEAMyW1Pnt2fdIz3MT4ZeiHxWra204SBA=; h=Message-ID:Date:From:To:Cc:Subject; b=kyvi/r2N+K/u/jeVmF2FzyE7eqWsYqnkfesCwxSrrWpZwxeFLCzh9ABDD4Rm3QI291WXKmN8A40N/I2V7VwK6TOg1fScB6tN5fvXja8O+ec0I8jl5h3fJ751MW9xpEqa8h7KDfXiQ/XLMfqF/TEhcLQVnreLp9pyXkFaMbnuA78= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dGGTEv1G; 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="dGGTEv1G" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EEA19C19425; Mon, 20 Apr 2026 18:10:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776708636; bh=WM5JLDywrrTEAMyW1Pnt2fdIz3MT4ZeiHxWra204SBA=; h=Date:From:To:Cc:Subject:From; b=dGGTEv1GCqfmV93L/FQGwa9Sfwc7GhHoskES4j87MTZ7FqaxDfzYKqSJDReQOmDnd AJTBVyO6UP0uNXCAES1mVmfGr767Ynlh/+cJRsUcWOb/WHjTqbzdeMIokQ9d4HPgys h00HjLaqQs/+JSTFjGB3ej6qZ2aK2GYLIx/R9d40zH4Cnd9hCUgXYkHieBmUgHD2eb C4fVcugW4G93axOz33OO4sWz/Vjv4oZhlGFL8igsVykf4BHMoVRkAZPIYzLtMSiPv5 RQ440lnBu/GOoITmyMy924SA2Lecyzgim/YFz3Vu9wA6MoCvE6AeGfH++LCbDXvlbd YkAwAX+vKGJkQ== Received: from rostedt by gandalf with local (Exim 4.99.1) (envelope-from ) id 1wEt6a-00000006nHn-0iuL; Mon, 20 Apr 2026 14:12:20 -0400 Message-ID: <20260420181151.771404678@kernel.org> User-Agent: quilt/0.69 Date: Mon, 20 Apr 2026 14:11:51 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Masami Hiramatsu , Mark Rutland , Mathieu Desnoyers , Andrew Morton Subject: [for-linus][PATCH 0/2] tracefs: Fixes for 7.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: tracefs fixes for v7.1: - Use list_add_tail_rcu() for walking eventfs children The children link list is protected by SRCU and list walkers can walk the list without the lock and only using SRCU. Using just list_add_tail() on weakly ordered architectures can cause issues. Instead use list_add_tail_rcu(). - Hold eventfs_mutex and SRCU for remount walk events The trace_apply_options() walks the tracefs_inodes where some are eventfs inodes and eventfs_remount() is called which in turn calls eventfs_set_attr(). This walk only holds normal RCU read locks, but the eventfs_mutex and SRCU should be held. Add a eventfs_remount_(un)lock() helpers to take the necessary locks before iterating the list. git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git tracefs/fixes Head SHA1: 07004a8c4b572171934390148ee48c4175c77eed David Carlier (2): eventfs: Use list_add_tail_rcu() for SRCU-protected children list eventfs: Hold eventfs_mutex and SRCU when remount walks events ---- fs/tracefs/event_inode.c | 16 +++++++++++++++- fs/tracefs/inode.c | 5 ++++- fs/tracefs/internal.h | 3 +++ 3 files changed, 22 insertions(+), 2 deletions(-)