From: Niklas Cassel <niklas.cassel@axis.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <mhocko@suse.com>
Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Niklas Cassel <niklass@axis.com>
Subject: [PATCH] locking/rwsem: fix down_write_killable for CONFIG_RWSEM_GENERIC_SPINLOCK
Date: Sat, 25 Feb 2017 01:17:53 +0100 [thread overview]
Message-ID: <1487981873-12649-1-git-send-email-niklass@axis.com> (raw)
From: Niklas Cassel <niklas.cassel@axis.com>
SIGKILL has been sent, but the task is stuck in down_read (after do_exit),
even though no task is doing down_write on the rwsem in question.
INFO: task libupnp:21868 blocked for more than 120 seconds.
Tainted: G O 4.9.11-devel #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
libupnp D 0 21868 1 0x08100008
Stack : 00000001 8ecf44a0 8ef644a0 8e06fe40 00000000 808b0000 00000001 00000000
00000001 77aab068 00000001 00000001 00000000 8ecf44a0 00400000 800d4d88
8ecf44a0 00000002 80698ac0 00000001 8c3f0544 00000001 00000000 8ecf44a0
00400000 80694a58 8ecf44a0 00000000 8ecf44a0 8c3f0544 8ecf44a0 80698ac8
8c3f0500 00000000 77a053b4 800454bc 8958dd68 8ef83d68 8ecf44a0 00000001
...
Call Trace:
[<806942b0>] __schedule+0x738/0xd48
[<80694a58>] schedule+0x44/0xb8
[<80698ac8>] __down_read+0xc8/0x124
[<8004c034>] do_exit+0x18c/0xa78
[<8004c9cc>] do_group_exit+0x5c/0xc4
[<8004ca54>] __wake_up_parent+0x0/0x24
This bug has already been fixed for CONFIG_RWSEM_XCHGADD_ALGORITHM in
commit 04cafed7fc19 ("locking/rwsem: Fix down_write_killable()"), however,
this bug also exists for CONFIG_RWSEM_GENERIC_SPINLOCK.
Cc: stable <stable@vger.kernel.org> # 4.7+
Fixes: d47996082f52 ("locking/rwsem: Introduce basis for down_write_killable()")
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
---
kernel/locking/rwsem-spinlock.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/kernel/locking/rwsem-spinlock.c b/kernel/locking/rwsem-spinlock.c
index 5eacab880f67..ab7271e16918 100644
--- a/kernel/locking/rwsem-spinlock.c
+++ b/kernel/locking/rwsem-spinlock.c
@@ -212,10 +212,9 @@ int __sched __down_write_common(struct rw_semaphore *sem, int state)
*/
if (sem->count == 0)
break;
- if (signal_pending_state(state, current)) {
- ret = -EINTR;
- goto out;
- }
+ if (signal_pending_state(state, current))
+ goto out_nolock;
+
set_current_state(state);
raw_spin_unlock_irqrestore(&sem->wait_lock, flags);
schedule();
@@ -223,12 +222,19 @@ int __sched __down_write_common(struct rw_semaphore *sem, int state)
}
/* got the lock */
sem->count = -1;
-out:
list_del(&waiter.list);
raw_spin_unlock_irqrestore(&sem->wait_lock, flags);
return ret;
+
+out_nolock:
+ list_del(&waiter.list);
+ if (!list_empty(&sem->wait_list))
+ __rwsem_do_wake(sem, 1);
+ raw_spin_unlock_irqrestore(&sem->wait_lock, flags);
+
+ return -EINTR;
}
void __sched __down_write(struct rw_semaphore *sem)
--
2.1.4
next reply other threads:[~2017-02-25 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 0:17 Niklas Cassel [this message]
2017-03-06 8:59 ` Niklas Cassel
2017-03-06 11:28 ` Peter Zijlstra
2017-03-16 11:14 ` [tip:locking/core] locking/rwsem: Fix down_write_killable() for CONFIG_RWSEM_GENERIC_SPINLOCK=y tip-bot for Niklas Cassel
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=1487981873-12649-1-git-send-email-niklass@axis.com \
--to=niklas.cassel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=niklass@axis.com \
--cc=peterz@infradead.org \
--cc=stable@vger.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
Powered by JetHome