From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [patch] rt,workqueue: Fix blocking call when !TASK_RUNNING splat in rescuer_thread()
Date: Sat, 27 Feb 2016 14:48:06 +0100 [thread overview]
Message-ID: <1456580886.3577.6.camel@gmail.com> (raw)
In-Reply-To: <1456575080.3577.3.camel@gmail.com>
On Sat, 2016-02-27 at 13:11 +0100, Mike Galbraith wrote:
> On Sat, 2016-02-27 at 10:16 +0100, Thomas Gleixner wrote:
> > On Sat, 27 Feb 2016, Mike Galbraith wrote:
> > > [ 0.221272] CPU: 1 PID: 69 Comm: khelper Not tainted 4.0.0-rt4
> > -lockdep #71
> >
> > Can to verify that against some less random rt version?
>
> Yeah, I'll remove the patch from 4.4-rt and see if it still happens.
> Patch has been moldering for quite a while.
Hohum, elves and gremlins at play I suppose. I think it's safe to say
oh, never mind to that one.
-Mike
prev parent reply other threads:[~2016-02-27 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 7:05 [patch] rt,workqueue: Fix blocking call when !TASK_RUNNING splat in rescuer_thread() Mike Galbraith
2016-02-27 7:09 ` [patch] drm,radeon,i915: use preempt_disable/enable_rt() where recommended Mike Galbraith
2016-02-27 7:34 ` [patch] locking/lglocks: use preempt_enable/disable_nort() in lg_double_lock/lg_double_unlock Mike Galbraith
2016-02-27 8:01 ` [patch] drm,i915: Use local_lock/unlock_irq() in intel_pipe_update_start/end() Mike Galbraith
2016-02-27 9:04 ` [patch] rt,workqueue: Fix blocking call when !TASK_RUNNING splat in rescuer_thread() Thomas Gleixner
2016-02-27 9:14 ` Thomas Gleixner
2016-02-27 9:16 ` Thomas Gleixner
2016-02-27 12:11 ` Mike Galbraith
2016-02-27 13:48 ` Mike Galbraith [this message]
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=1456580886.3577.6.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.