From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1425366AbcBRIOL (ORCPT ); Thu, 18 Feb 2016 03:14:11 -0500 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:57620 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1425120AbcBRIOI (ORCPT ); Thu, 18 Feb 2016 03:14:08 -0500 X-Original-SENDERIP: 156.147.1.125 X-Original-MAILFROM: byungchul.park@lge.com X-Original-SENDERIP: 10.177.222.33 X-Original-MAILFROM: byungchul.park@lge.com Date: Thu, 18 Feb 2016 17:13:26 +0900 From: Byungchul Park To: Peter Zijlstra 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() Message-ID: <20160218081326.GF5972@X58A-UD3R> References: <1455700311-2308-1-git-send-email-byungchul.park@lge.com> <20160217104049.GB25010@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160217104049.GB25010@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?