+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -423,6 +423,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
net-x25-fix-use-after-free-in-x25_kill_by_neigh.patch
net-hip04-fix-rx-buffer-leak-on-build_skb-failure.patch
proc-fix-broken-error-paths-for-namespace-links.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
ila-reload-ipv6-header-after-pskb_may_pull-in-checksum-adjust.patch
mac802154-llsec-reject-frames-shorter-than-the-authentication-tag.patch
+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -423,6 +423,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
net-x25-fix-use-after-free-in-x25_kill_by_neigh.patch
net-hip04-fix-rx-buffer-leak-on-build_skb-failure.patch
proc-fix-broken-error-paths-for-namespace-links.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
ice-use-read_once-to-access-cached-phc-time.patch
ila-reload-ipv6-header-after-pskb_may_pull-in-checksum-adjust.patch
+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -423,6 +423,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
net-x25-fix-use-after-free-in-x25_kill_by_neigh.patch
net-hip04-fix-rx-buffer-leak-on-build_skb-failure.patch
proc-fix-broken-error-paths-for-namespace-links.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
ksmbd-defer-destroy_previous_session-until-after-ntlm-authentication.patch
ice-use-read_once-to-access-cached-phc-time.patch
+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -483,6 +483,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
net-hip04-fix-rx-buffer-leak-on-build_skb-failure.patch
proc-fix-broken-error-paths-for-namespace-links.patch
ice-fix-ptp-call-trace-during-ptp-release.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
ksmbd-defer-destroy_previous_session-until-after-ntlm-authentication.patch
ice-reject-out-of-range-ptype-in-ice_parser_profile_init.patch
+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -483,6 +483,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
s390-ptff-export-ptff_function_mask.patch
ptp-ptp_s390-add-missing-facility-check.patch
ice-fix-ptp-call-trace-during-ptp-release.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
super-fix-emergency-thaw-deadlock-on-frozen-block-devices.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
smb-client-handle-status_stopped_on_symlink-responses-without-a-symlink-target.patch
+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -477,6 +477,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
net-x25-fix-use-after-free-in-x25_kill_by_neigh.patch
net-hip04-fix-rx-buffer-leak-on-build_skb-failure.patch
proc-fix-broken-error-paths-for-namespace-links.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
ksmbd-defer-destroy_previous_session-until-after-ntlm-authentication.patch
ice-use-read_once-to-access-cached-phc-time.patch
+++ /dev/null
-From 1a087033a6bad73b4140020b40e819b0933aafc3 Mon Sep 17 00:00:00 2001
-From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
-Date: Fri, 17 Jul 2026 11:51:59 +0900
-Subject: selftests/ftrace: Reset triggers at top level before instance loop
-
-From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
-commit 1a087033a6bad73b4140020b40e819b0933aafc3 upstream.
-
-When running instance tests, 'ftracetest' creates a new ftrace instance
-and runs the tests inside it. Before starting each test, it executes
-'initialize_system()' to reset the ftrace state to initial-state.
-
-However, since 'initialize_system()' is executed in the context of the
-instance directory, it only cleans up triggers and filters of that
-instance.
-Any triggers or dynamic events left behind in the top-level instance by
-previous failed top-level tests, are left completely untouched. These
-top-level leftovers can cause subsequent instance-based tests to fail
-or even crash the kernel.
-
-Fix this by executing 'initialize_system()' in the top-level tracing
-directory once before entering the instance loop.
-
-Cc: stable@vger.kernel.org
-Link: https://patch.msgid.link/178425671889.84440.9477850701738666404.stgit@devnote2
-Fixes: b5b77be812de ("selftests: ftrace: Allow some tests to be run in a tracing instance")
-Assisted-by: Antigravity:gemini-3.5-flash
-Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
-Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- tools/testing/selftests/ftrace/ftracetest | 1 +
- 1 file changed, 1 insertion(+)
-
---- a/tools/testing/selftests/ftrace/ftracetest
-+++ b/tools/testing/selftests/ftrace/ftracetest
-@@ -503,6 +503,7 @@ for t in $TEST_CASES; do
- done
-
- # Test on instance loop
-+(cd $TRACING_DIR; initialize_system)
- INSTANCE=" (instance) "
- for t in $TEST_CASES; do
- test_on_instance $t || continue
s390-ptff-export-ptff_function_mask.patch
ptp-ptp_s390-add-missing-facility-check.patch
ice-fix-ptp-call-trace-during-ptp-release.patch
-selftests-ftrace-reset-triggers-at-top-level-before-instance-loop.patch
super-fix-emergency-thaw-deadlock-on-frozen-block-devices.patch
rbd-reset-positive-result-codes-to-zero-in-object-map-update-path.patch
smb-client-handle-status_stopped_on_symlink-responses-without-a-symlink-target.patch