From: Byungchul Park <byungchul.park@lge.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: willy@linux.intel.com, akpm@linux-foundation.org,
mingo@kernel.org, linux-kernel@vger.kernel.org,
akinobu.mita@gmail.com, jack@suse.cz,
sergey.senozhatsky.work@gmail.com, peter@hurleysoftware.com
Subject: Re: [PATCH v3] lock/semaphore: Avoid an unnecessary deadlock within up()
Date: Thu, 18 Feb 2016 17:13:26 +0900 [thread overview]
Message-ID: <20160218081326.GF5972@X58A-UD3R> (raw)
In-Reply-To: <20160217104049.GB25010@twins.programming.kicks-ass.net>
On Wed, Feb 17, 2016 at 11:40:49AM +0100, Peter Zijlstra wrote:
> Mucking with the semaphore implementation just because printk() is
> terminally broken shite really doesn't fly.
Jan is currently working on the terminally broken shite, and I expect it
makes printk() robuster. I just tried this patch because I though the
semaphore also need to be fixed and furthermore it can fix a deadlock by
removing the waiting within trylock. I think it's reasonable. Wrong?
prev parent reply other threads:[~2016-02-18 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 9:11 [PATCH v3] lock/semaphore: Avoid an unnecessary deadlock within up() Byungchul Park
2016-02-17 9:28 ` Ingo Molnar
2016-02-18 8:00 ` Byungchul Park
2016-03-09 2:00 ` Byungchul Park
2016-03-09 6:07 ` Byungchul Park
2016-03-10 0:38 ` Byungchul Park
2016-03-10 1:12 ` Byungchul Park
2016-02-17 10:40 ` Peter Zijlstra
2016-02-18 8:13 ` Byungchul Park [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=20160218081326.GF5972@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=willy@linux.intel.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