Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936296AbaFJDVS (ORCPT ); Mon, 9 Jun 2014 23:21:18 -0400 Received: from mail-ig0-f176.google.com ([209.85.213.176]:59540 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932844AbaFJDVO (ORCPT ); Mon, 9 Jun 2014 23:21:14 -0400 MIME-Version: 1.0 In-Reply-To: <20140609202335.980283946@linutronix.de> References: <20140609201118.387571774@linutronix.de> <20140609202335.980283946@linutronix.de> Date: Mon, 9 Jun 2014 20:21:13 -0700 X-Google-Sender-Auth: DStdn_fT8sSZGe9BFQCYgkdyikU Message-ID: Subject: Re: [patch V3 1/7] rtmutex: Deobfuscate chain walk From: Jason Low To: Thomas Gleixner Cc: LKML , Steven Rostedt , Peter Zijlstra , Ingo Molnar , Lai Jiangshan , Jason Low , Brad Mouring Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 9, 2014 at 1:28 PM, Thomas Gleixner wrote: > There is no point to keep the task ref across the check for lock > owner. Drop the ref before that, so the protection context is clear. > > Found while documenting the chain walk. > > Signed-off-by: Thomas Gleixner Reviewed-by: Jason Low -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/