From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752742AbcJNR5S (ORCPT ); Fri, 14 Oct 2016 13:57:18 -0400 Received: from mga02.intel.com ([134.134.136.20]:2415 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751986AbcJNR5K (ORCPT ); Fri, 14 Oct 2016 13:57:10 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,493,1473145200"; d="scan'208";a="19644374" From: "Luck, Tony" To: Greg Kroah-Hartman Cc: Tony Luck , linux-kernel@vger.kernel.org Subject: [PATCH] kernfs: Add noop_fsync to supported kernfs_file_fops Date: Fri, 14 Oct 2016 10:56:42 -0700 Message-Id: <1476467802-11369-1-git-send-email-tony.luck@intel.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Tony Luck If you edit a kernfs backed file with vi(1), you see an ugly error message when you write the file because vi tries to fsync(2) the file after writing, which fails. We have noop_fsync() for this, use it. Signed-off-by: Tony Luck --- fs/kernfs/file.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/kernfs/file.c b/fs/kernfs/file.c index 2bcb86e6e6ca..78219d5644e9 100644 --- a/fs/kernfs/file.c +++ b/fs/kernfs/file.c @@ -911,6 +911,7 @@ const struct file_operations kernfs_file_fops = { .open = kernfs_fop_open, .release = kernfs_fop_release, .poll = kernfs_fop_poll, + .fsync = noop_fsync, }; /** -- 2.5.0