From: Michal Hocko <mhocko@kernel.org>
To: Yunfeng Cui <cui.yunfeng@zte.com.cn>
Cc: christian@brauner.io, ldv@altlinux.org, luto@amacapital.net,
keescook@chromium.org, wad@chromium.org, arunks@codeaurora.org,
guro@fb.com, peterz@infradead.org, elena.reshetova@intel.com,
joel@joelfernandes.org, mingo@kernel.org,
akpm@linux-foundation.org, aarcange@redhat.com,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
jiang.xuexin@zte.com.cn, wang.yi59@zte.com.cn,
xue.zhihong@zte.com.cn, Thomas Gleixner <tglx@linutronix.de>,
Darren Hart <dvhart@infradead.org>
Subject: Re: [PATCH] futex: robust futex maybe never be awaked, on rare situation.
Date: Mon, 23 Sep 2019 12:55:14 +0200 [thread overview]
Message-ID: <20190923105514.GJ6016@dhcp22.suse.cz> (raw)
In-Reply-To: <1569208700-24044-1-git-send-email-cui.yunfeng@zte.com.cn>
[Cc more futex people]
On Mon 23-09-19 11:18:20, Yunfeng Cui wrote:
> I use model checker find a issue of robust and pi futex. On below
> situation, the owner can't find something in pi_state_list, while
> the requester will be blocked, never be awaked.
>
> CPU0 CPU1
> futex_lock_pi
> /*some cs code*/
> futex_lock_pi
> futex_lock_pi_atomic
> ...
> newval = uval | FUTEX_WAITERS;
> ret = lock_pi_update_atomic(uaddr, uval, newval);
> ...
> attach_to_pi_owner
> ....
> p = find_get_task_by_vpid(pid);
> if (!p)
> return handle_exit_race(uaddr, uval, NULL);
> ....
> raw_spin_lock_irq(&p->pi_lock);
> ....
> pi_state = alloc_pi_state();
> ....
> do_exit->mm_release
> if (unlikely(tsk->robust_list)) {
> exit_robust_list(tsk);
> tsk->robust_list = NULL;
> }
> if (unlikely(!list_empty(&tsk->pi_state_list)))
> exit_pi_state_list(tsk); /*WILL MISS*/
> list_add(&pi_state->list, &p->pi_state_list);
> WILL BLOCKED, NEVER WAKEUP!
>
> Signed-off-by: Yunfeng Cui <cui.yunfeng@zte.com.cn>
> Reviewed-by: Bo Wang <wang.bo116@zte.com.cn>
> Reviewed-by: Yi Wang <wang.yi59@zte.com.cn>
> ---
> kernel/fork.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 53e780748fe3..58b90f21dac4 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1277,15 +1277,16 @@ void mm_release(struct task_struct *tsk, struct mm_struct *mm)
> if (unlikely(tsk->robust_list)) {
> exit_robust_list(tsk);
> tsk->robust_list = NULL;
> + /*Check pi_state_list of task on pi_lock be acquired*/
> + exit_pi_state_list(tsk);
> }
> #ifdef CONFIG_COMPAT
> if (unlikely(tsk->compat_robust_list)) {
> compat_exit_robust_list(tsk);
> tsk->compat_robust_list = NULL;
> + exit_pi_state_list(tsk);
> }
> #endif
> - if (unlikely(!list_empty(&tsk->pi_state_list)))
> - exit_pi_state_list(tsk);
> #endif
>
> uprobe_free_utask(tsk);
> --
> 2.15.2
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-09-23 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 3:18 Yunfeng Cui
2019-09-23 10:55 ` Michal Hocko [this message]
2019-09-23 13:05 ` Peter Zijlstra
2019-09-23 14:09 ` 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=20190923105514.GJ6016@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=christian@brauner.io \
--cc=cui.yunfeng@zte.com.cn \
--cc=dvhart@infradead.org \
--cc=elena.reshetova@intel.com \
--cc=guro@fb.com \
--cc=jiang.xuexin@zte.com.cn \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wad@chromium.org \
--cc=wang.yi59@zte.com.cn \
--cc=xue.zhihong@zte.com.cn \
/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®