From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755745AbbCCDT0 (ORCPT ); Mon, 2 Mar 2015 22:19:26 -0500 Received: from mail-pd0-f177.google.com ([209.85.192.177]:34747 "EHLO mail-pd0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754859AbbCCDTY (ORCPT ); Mon, 2 Mar 2015 22:19:24 -0500 Date: Tue, 3 Mar 2015 08:49:10 +0530 From: Tapasweni Pathak To: viro@zeniv.linux.org.uk, akpm@linux-foundation.org, tglx@linutronix.de, ionut.m.alexa@gmail.com, paulmcquad@gmail.com, linux-kernel@vger.kernel.org Cc: tapaswenipathak@gmail.com Subject: [PATCH] kernel: Unlock after locking Message-ID: <20150303031910.GA25670@kt-Inspiron-3542> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Release lock before returning. Signed-off-by: Tapasweni Pathak --- I'm not sure if this is a bug, it seems like it is intentional, but there is no comment or anything like that which confirms this. kernel/acct.c | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/acct.c b/kernel/acct.c index e6c10d1a..f592218 100644 --- a/kernel/acct.c +++ b/kernel/acct.c @@ -161,6 +161,7 @@ again: acct_put(res); goto again; } + mutex_unlock(&res->lock); return res; } -- 1.7.9.5