mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Sebastian Sewior <bigeasy@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v4.4.3-rt9
Date: Mon, 29 Feb 2016 16:00:18 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1602291538590.3638@nanos> (raw)
In-Reply-To: <1456756060.3488.120.camel@gmail.com>

On Mon, 29 Feb 2016, Mike Galbraith wrote:

> On Mon, 2016-02-29 at 13:46 +0100, Thomas Gleixner wrote:
> > Dear RT folks!
> > 
> > I'm pleased to announce the v4.4.3-rt9 patch set. v4.4.2-rt7 and v4.4.3-rt8
> > are non-announced updates to incorporate the linux-4.4.y stable tree.
> > 
> > There is one change caused by the 4.4.3 update:
> > 
> >   The relaxed handling of dump_stack() on RT has been dropped as there is
> >   actually a potential deadlock lurking around the corner. See: commit
> >   d7ce36924344 upstream. This does not effect the other facilities which
> >   gather stack traces.
> 
> Hrm.  I had rolled that dropped bit forward as below.  I was given
> cause to do a very large pile of ltp oom4 testing (rt kernels will
> livelock due to waitqueue workers waiting for kthreadd to get memory to
> spawn a kworker thread, while stuck kworker holds manager mutex, unless
> workers are run as rt tasks to keep us from getting that depleted in
> the first place), which gives it oodles of exercise, and all _seemed_
> well.  Only seemed?

Well, it will work nicely as long as you don't trigger a back trace in hard
irq context. Hmm?

Thanks,

	tglx

  reply	other threads:[~2016-02-29 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 12:46 Thomas Gleixner
2016-02-29 14:27 ` Mike Galbraith
2016-02-29 15:00   ` Thomas Gleixner [this message]
2016-02-29 15:09     ` Mike Galbraith
2016-02-29 19:54 ` Steven Rostedt
2016-02-29 20:11   ` 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=alpine.DEB.2.11.1602291538590.3638@nanos \
    --to=tglx@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=umgwanakikbuti@gmail.com \
    /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®