From: "tip-bot2 for Dan Carpenter" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: core/rseq] rseq: Delete duplicate if statement in rseq_virt_userspace_exit()
Date: Tue, 18 Nov 2025 14:57:35 -0000 [thread overview]
Message-ID: <176347785546.498.16294534513000187167.tip-bot2@tip-bot2> (raw)
In-Reply-To: <aRxP3YcwscrP1BU_@stanley.mountain>
The following commit has been merged into the core/rseq branch of tip:
Commit-ID: 80adaccf0e1c8c8fff44be2d959f6dba80af0491
Gitweb: https://git.kernel.org/tip/80adaccf0e1c8c8fff44be2d959f6dba80af0491
Author: Dan Carpenter <dan.carpenter@linaro.org>
AuthorDate: Tue, 18 Nov 2025 13:52:13 +03:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Tue, 18 Nov 2025 15:56:55 +01:00
rseq: Delete duplicate if statement in rseq_virt_userspace_exit()
This if statement is indented weirdly. It's a duplicate and doesn't
affect runtime (beyond wasting a little time). Delete it.
Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://patch.msgid.link/aRxP3YcwscrP1BU_@stanley.mountain
---
include/linux/rseq.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/rseq.h b/include/linux/rseq.h
index b5e4803..bf8a6bf 100644
--- a/include/linux/rseq.h
+++ b/include/linux/rseq.h
@@ -126,7 +126,6 @@ static inline void rseq_force_update(void)
*/
static inline void rseq_virt_userspace_exit(void)
{
- if (current->rseq.event.sched_switch)
/*
* The generic optimization for deferring RSEQ updates until the next
* exit relies on having a dedicated TIF_RSEQ.
next prev parent reply other threads:[~2025-11-18 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 10:52 [PATCH] rseq: Delete duplicate if statement in rseq_virt_userspace_exit() Dan Carpenter
2025-11-18 14:57 ` tip-bot2 for Dan Carpenter [this message]
2025-11-18 14:58 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176347785546.498.16294534513000187167.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox