From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753490AbdDKF01 (ORCPT ); Tue, 11 Apr 2017 01:26:27 -0400 Received: from mail-pf0-f193.google.com ([209.85.192.193]:33854 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752214AbdDKF00 (ORCPT ); Tue, 11 Apr 2017 01:26:26 -0400 From: Pushkar Jambhlekar To: Dan Williams Cc: linux-kernel@vger.kernel.org, Pushkar Jambhlekar Subject: [PATCH 1/2] drivers/dax: Avoiding potential deadlock Date: Tue, 11 Apr 2017 10:56:20 +0530 Message-Id: <1491888381-7726-1-git-send-email-pushkar.iit@gmail.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: ,> References: ,> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org dax_dev_huge_fault returning without releasing lock. Making code change to avoid this situation Signed-off-by: Pushkar Jambhlekar --- drivers/dax/dax.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dax/dax.c b/drivers/dax/dax.c index 0d1ca24..fd9c4db 100644 --- a/drivers/dax/dax.c +++ b/drivers/dax/dax.c @@ -590,7 +590,7 @@ static int dax_dev_huge_fault(struct vm_fault *vmf, rc = __dax_dev_pud_fault(dax_dev, vmf); break; default: - return VM_FAULT_FALLBACK; + rc = VM_FAULT_FALLBACK; } rcu_read_unlock(); -- 2.7.4