From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f67.google.com ([209.85.218.67]:41618 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726812AbeHZXRr (ORCPT ); Sun, 26 Aug 2018 19:17:47 -0400 Received: by mail-oi0-f67.google.com with SMTP id k12-v6so23712771oiw.8 for ; Sun, 26 Aug 2018 12:34:19 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1535300717-26686-7-git-send-email-amir73il@gmail.com> References: <1535300717-26686-1-git-send-email-amir73il@gmail.com> <1535300717-26686-7-git-send-email-amir73il@gmail.com> From: Miklos Szeredi Date: Sun, 26 Aug 2018 21:34:18 +0200 Message-ID: Subject: Re: [PATCH v2 6/6] vfs: fix sync_file_range syscall on an overlayfs file To: Amir Goldstein Cc: Al Viro , Dave Chinner , overlayfs , linux-fsdevel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Aug 26, 2018 at 6:25 PM, Amir Goldstein wrote: > For an overlayfs file/inode, page io is operating on the real underlying > file, so sync_file_range() should operate on the real underlying file > mapping to take affect. The man page tells us that this syscall basically gives no guarantees at all and shouldn't be used in portable programs. So, I'd just let the non-functionality be for now. If someone complains of a regression (unlikely) we can look into it. Thanks, Miklos