From: Tom Zanussi <zanussi@kernel.org>
To: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: rostedt@goodmis.org, tglx@linutronix.de, C.Emde@osadl.org,
jkacur@redhat.com, bigeasy@linutronix.de,
daniel.wagner@siemens.com, julia@ni.com, amartin@nvidia.com
Subject: [PATCH 06/13] softirq: Avoid "local_softirq_pending" messages if ksoftirqd is blocked
Date: Mon, 8 Apr 2019 14:14:08 -0500 [thread overview]
Message-ID: <07c2c239ec6a9cc26b4d4c149dc76e88462c68d9.1554737688.git.tom.zanussi@linux.intel.com> (raw)
In-Reply-To: <cover.1554737688.git.tom.zanussi@linux.intel.com>
In-Reply-To: <cover.1554737688.git.tom.zanussi@linux.intel.com>
4.14.109-rt58-rc1 stable review patch.
If anyone has any objections, please let me know.
------------------
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
[ Upstream commit 2cf32c1a3d9352df8017dbf84a1462c4a60a1826 ]
If the ksoftirqd thread has a softirq pending and is blocked on the
`local_softirq_locks' lock then softirq_check_pending_idle() won't
complain because the "lock owner" will mask away this softirq from the
mask of pending softirqs.
If ksoftirqd has an additional softirq pending then it won't be masked
out because we never look at ksoftirqd's mask.
If there are still pending softirqs while going to idle check
ksoftirqd's and ktimersfotd's mask before complaining about unhandled
softirqs.
Cc: stable-rt@vger.kernel.org
Tested-by: Juri Lelli <juri.lelli@redhat.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
---
kernel/softirq.c | 57 ++++++++++++++++++++++++++++++++++++++++----------------
1 file changed, 41 insertions(+), 16 deletions(-)
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 583c9ecf04e3..be752eadfc68 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -92,6 +92,31 @@ static inline void softirq_clr_runner(unsigned int sirq)
sr->runner[sirq] = NULL;
}
+static bool softirq_check_runner_tsk(struct task_struct *tsk,
+ unsigned int *pending)
+{
+ bool ret = false;
+
+ if (!tsk)
+ return ret;
+
+ /*
+ * The wakeup code in rtmutex.c wakes up the task
+ * _before_ it sets pi_blocked_on to NULL under
+ * tsk->pi_lock. So we need to check for both: state
+ * and pi_blocked_on.
+ */
+ raw_spin_lock(&tsk->pi_lock);
+ if (tsk->pi_blocked_on || tsk->state == TASK_RUNNING) {
+ /* Clear all bits pending in that task */
+ *pending &= ~(tsk->softirqs_raised);
+ ret = true;
+ }
+ raw_spin_unlock(&tsk->pi_lock);
+
+ return ret;
+}
+
/*
* On preempt-rt a softirq running context might be blocked on a
* lock. There might be no other runnable task on this CPU because the
@@ -104,6 +129,7 @@ static inline void softirq_clr_runner(unsigned int sirq)
*/
void softirq_check_pending_idle(void)
{
+ struct task_struct *tsk;
static int rate_limit;
struct softirq_runner *sr = this_cpu_ptr(&softirq_runners);
u32 warnpending;
@@ -113,24 +139,23 @@ void softirq_check_pending_idle(void)
return;
warnpending = local_softirq_pending() & SOFTIRQ_STOP_IDLE_MASK;
+ if (!warnpending)
+ return;
for (i = 0; i < NR_SOFTIRQS; i++) {
- struct task_struct *tsk = sr->runner[i];
+ tsk = sr->runner[i];
- /*
- * The wakeup code in rtmutex.c wakes up the task
- * _before_ it sets pi_blocked_on to NULL under
- * tsk->pi_lock. So we need to check for both: state
- * and pi_blocked_on.
- */
- if (tsk) {
- raw_spin_lock(&tsk->pi_lock);
- if (tsk->pi_blocked_on || tsk->state == TASK_RUNNING) {
- /* Clear all bits pending in that task */
- warnpending &= ~(tsk->softirqs_raised);
- warnpending &= ~(1 << i);
- }
- raw_spin_unlock(&tsk->pi_lock);
- }
+ if (softirq_check_runner_tsk(tsk, &warnpending))
+ warnpending &= ~(1 << i);
+ }
+
+ if (warnpending) {
+ tsk = __this_cpu_read(ksoftirqd);
+ softirq_check_runner_tsk(tsk, &warnpending);
+ }
+
+ if (warnpending) {
+ tsk = __this_cpu_read(ktimer_softirqd);
+ softirq_check_runner_tsk(tsk, &warnpending);
}
if (warnpending) {
--
2.14.1
next prev parent reply other threads:[~2019-04-08 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 19:14 [PATCH 00/13] Linux 4.14.109-rt58-rc1 Tom Zanussi
2019-04-08 19:14 ` [PATCH 01/13] arm64: fpsimd: use preemp_disable in addition to local_bh_disable() Tom Zanussi
2019-04-08 19:14 ` [PATCH 02/13] sched/fair: Robustify CFS-bandwidth timer locking Tom Zanussi
2019-04-08 19:14 ` [PATCH 03/13] sched/fair: Make the hrtimers non-hard again Tom Zanussi
2019-04-08 19:14 ` [PATCH 04/13] locking/rt-mutex: Flush block plug on __down_read() Tom Zanussi
2019-04-08 19:14 ` [PATCH 05/13] rtmutex/rwlock: preserve state like a sleeping lock Tom Zanussi
2019-04-08 19:14 ` Tom Zanussi [this message]
2019-04-08 19:14 ` [PATCH 07/13] softirq: Avoid "local_softirq_pending" messages if task is in cpu_chill() Tom Zanussi
2019-04-08 19:14 ` [PATCH 08/13] hrtimer: Don't lose state " Tom Zanussi
2019-04-08 19:14 ` [PATCH 09/13] x86: lazy-preempt: properly check against preempt-mask Tom Zanussi
2019-04-08 19:14 ` [PATCH 10/13] hrtimer: cpu_chill(): save task state in ->saved_state() Tom Zanussi
2019-04-08 19:14 ` [PATCH 11/13] tty/sysrq: Convert show_lock to raw_spinlock_t Tom Zanussi
2019-04-08 19:14 ` [PATCH 12/13] powerpc/pseries/iommu: Use a locallock instead local_irq_save() Tom Zanussi
2019-04-08 19:14 ` [PATCH 13/13] Linux 4.14.109-rt58 Tom Zanussi
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=07c2c239ec6a9cc26b4d4c149dc76e88462c68d9.1554737688.git.tom.zanussi@linux.intel.com \
--to=zanussi@kernel.org \
--cc=C.Emde@osadl.org \
--cc=amartin@nvidia.com \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®