From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: peterz@infradead.org
Cc: tglx@linutronix.de, mingo@kernel.org, akpm@linux-foundation.org,
mgorman@techsingularity.net, mhocko@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: x86_64 Question: Are concurrent IPI requests safe?
Date: Thu, 12 May 2016 06:56:25 +0900 [thread overview]
Message-ID: <201605120656.BHB73494.tOFMOFOLFQHVJS@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20160511174630.GI3192@twins.programming.kicks-ass.net>
Peter Zijlstra wrote:
> On Thu, May 12, 2016 at 12:19:07AM +0900, Tetsuo Handa wrote:
> > Well, I came to feel that this is caused by down_write_killable() bug.
> > I guess we should fix down_write_killable() bug first.
>
> There's a patch you can try in that thread...
>
> lkml.kernel.org/r/20160511094128.GB3190@twins.programming.kicks-ass.net
>
OK. Applying that patch on next-20160511 seems to fix this problem.
Please send it to linux-next tree. Thank you.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-11 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 10:58 [next-20160506 mm,smp] hang up at csd_lock_wait() from drain_all_pages() Tetsuo Handa
2016-05-09 14:54 ` x86_64 Question: Are concurrent IPI requests safe? Tetsuo Handa
2016-05-09 16:54 ` Thomas Gleixner
2016-05-11 13:19 ` Tetsuo Handa
2016-05-11 13:39 ` Peter Zijlstra
2016-05-11 14:09 ` Tetsuo Handa
2016-05-11 14:33 ` Thomas Gleixner
2016-05-11 15:19 ` Tetsuo Handa
2016-05-11 17:46 ` Peter Zijlstra
2016-05-11 21:56 ` Tetsuo Handa [this message]
2016-05-11 14:13 ` 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=201605120656.BHB73494.tOFMOFOLFQHVJS@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox