From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: DIXLOR <dixlor@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: dump_stack: avoid potential deadlocks
Date: Tue, 8 Mar 2016 10:34:04 +0100 [thread overview]
Message-ID: <20160308093404.GB21842@linutronix.de> (raw)
In-Reply-To: <56D24D50.6010500@gmail.com>
* DIXLOR | 2016-02-28 04:28:48 [+0300]:
>What do you think about commit e31e4672559674b0950885465a42968a86865d42
>
>https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/diff/lib/dump_stack.c?id=v4.4.3&id2=v4.4.2
>
>In RT instead preempt_disable() use migrate_disable()
What are you trying to say? What is the problem?
Sebastian
prev parent reply other threads:[~2016-03-08 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 1:28 dump_stack: avoid potential deadlocks DIXLOR
2016-03-08 9:34 ` Sebastian Andrzej Siewior [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=20160308093404.GB21842@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=dixlor@gmail.com \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).