From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 930ACC10F13 for ; Mon, 8 Apr 2019 14:36:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 61FB320818 for ; Mon, 8 Apr 2019 14:36:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554734166; bh=0XEJ92dboX6Pv8/yoSOUcqcrlEpYkX5YkgJP4sX63rg=; h=From:To:Cc:Subject:Date:List-ID:From; b=nV7hlePCIc6eqOt3xhJ129gyPtgYzI5lW31dZz39/pXAodpP8MTcTuosq6k3Lih8G 48P9ZWTgWckDvL3J9xdN/sT7nwPHPj2clUuC0sIcD3bW2KlsoXacfKZLLk1pMo823H Y4rukSFAMzG/Japyqi7RI5jPdKZUrjoSztWn0hlY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727161AbfDHOgE (ORCPT ); Mon, 8 Apr 2019 10:36:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:60498 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726633AbfDHOgE (ORCPT ); Mon, 8 Apr 2019 10:36:04 -0400 Received: from tleilax.poochiereds.net (cpe-71-70-156-158.nc.res.rr.com [71.70.156.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 167D120818; Mon, 8 Apr 2019 14:36:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554734163; bh=0XEJ92dboX6Pv8/yoSOUcqcrlEpYkX5YkgJP4sX63rg=; h=From:To:Cc:Subject:Date:From; b=SvuXupsAF2q64MNCBGaPqv3ITd6EoNMvp/oXZKFN4mkgpQIBNxyOBFXsQ3hEEgCrF pN3IN3QujqjxyXE3oqeHQ3GbxG7dsyTltq4jXcl8KBtx5oTJW12wVUNPZrTPFbUJfe 3cSaibuyIQNGMPJAeL3DJ79TtiF1OZsx7LnSMXMw= From: Jeff Layton To: zyan@redhat.com, sage@redhat.com, idryomov@gmail.com Cc: ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: [PATCH] ceph: remove superfluous inode_lock in ceph_fsync Date: Mon, 8 Apr 2019 10:36:01 -0400 Message-Id: <20190408143601.27752-1-jlayton@kernel.org> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Originally, filemap_write_and_wait took the i_mutex internally, but commit 02c24a82187d pushed the mutex acquisition into the individual fsync routines, leaving it up to the subsystem maintainers to remove it if it wasn't needed. For ceph, I see no reason to take the inode_lock here. All of the operations inside that lock are protected by their own locking. Signed-off-by: Jeff Layton --- fs/ceph/caps.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c index 36a8dc699448..f976939f771f 100644 --- a/fs/ceph/caps.c +++ b/fs/ceph/caps.c @@ -2257,8 +2257,6 @@ int ceph_fsync(struct file *file, loff_t start, loff_t end, int datasync) if (datasync) goto out; - inode_lock(inode); - dirty = try_flush_caps(inode, &flush_tid); dout("fsync dirty caps are %s\n", ceph_cap_string(dirty)); @@ -2273,7 +2271,6 @@ int ceph_fsync(struct file *file, loff_t start, loff_t end, int datasync) ret = wait_event_interruptible(ci->i_cap_wq, caps_are_flushed(inode, flush_tid)); } - inode_unlock(inode); out: dout("fsync %p%s result=%d\n", inode, datasync ? " datasync" : "", ret); return ret; -- 2.20.1