From patchwork Thu Apr 11 17:00:42 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Amir Goldstein X-Patchwork-Id: 10896449 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id B07DF1390 for ; Thu, 11 Apr 2019 17:00:58 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id A037028DBC for ; Thu, 11 Apr 2019 17:00:58 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 9E94E28DCD; Thu, 11 Apr 2019 17:00:58 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=unavailable version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 221D528DD4 for ; Thu, 11 Apr 2019 17:00:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726912AbfDKRAw (ORCPT ); Thu, 11 Apr 2019 13:00:52 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:38207 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726842AbfDKRAw (ORCPT ); Thu, 11 Apr 2019 13:00:52 -0400 Received: by mail-wr1-f68.google.com with SMTP id k11so8322878wro.5; Thu, 11 Apr 2019 10:00:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id; bh=cbvlBAsgmPq0wjmomYJoGS+b4tJiSIC7oCGIAQBbd7c=; b=Ccd6EU6a5WjkuTHIFIyrlSdUhoW/I/CLfdyU535V3DX7bvrJB+JXDGNTN3mks4u0Gs J0RVh8jjYOw/HDIXcyD39mvYUwZ+E8Ug1YDPeOieh5EeZjnM1dZKyKG2Rq17a0Mz3wVy LibGy87EvYIY+hvUwXP5nfNDr+WQdvXIF5n99Vjx1Q/ItQXmJMdq1jxnuddiJSHr+nVB fXlUaNL1iO+/rlKERs56f+OtEPj73Vj4w+Y6dC2YYpOlMQowmK6Y/jYx9qHzifZScueN cqduKct7ujQ8g186ZtRFCSd5LcpDbcjkDLMoTGGJDTLD0gcgbsvOWPSnf7mlECFX7qWq ppJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=cbvlBAsgmPq0wjmomYJoGS+b4tJiSIC7oCGIAQBbd7c=; b=XN69+ePlc2Oo9Kj9Wkkoah5lg+QcrWHrV9A4SC6Kb31/jbGAIyxUMQMqd42xHAWh3I ZFOJTmlrONHNFZVWUVSr88FC+WfxJijj3u3HxmsYGrquDjfTr7dzO/3i/tOvQVe4q3Ew ehVv52r+Dbw7kLCw/3zTvky0fP3zaVo5AdU9lBxFb0VyL6uLM4PeV/o0hhU1tyF8mZfe l+r+TMUJeXtSBo/HmcY5dnluwEcHjLplamV6KwZgYoTmsP7yzf7kvQCwWq442b5jgvQW PioAIv3u8JSkib9KhsBYN+RLfy81IRrLKkg6SN0pADYpYsCRHHofi8tx5J/FgdQs7+GE 0VGQ== X-Gm-Message-State: APjAAAXM9HG/+aj+aWMPcFijEeaG9UxDEHawSJuRPrVJsrydTULGAaYq LtdbyaHT3v7FDN1P4VXeMLc= X-Google-Smtp-Source: APXvYqwrJROnJ32SBXYKya9JKylyFA28nM2YwSh7np6B+3CCVnWy3wfueDzSzw85ynI6Z5EBS5ckeQ== X-Received: by 2002:adf:e4c2:: with SMTP id v2mr31414912wrm.124.1555002049706; Thu, 11 Apr 2019 10:00:49 -0700 (PDT) Received: from localhost.localdomain ([5.102.238.208]) by smtp.gmail.com with ESMTPSA id r6sm5071353wmc.11.2019.04.11.10.00.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Apr 2019 10:00:48 -0700 (PDT) From: Amir Goldstein To: Andrew Morton Cc: Jan Kara , Dave Chinner , Al Viro , linux-mm@kvack.org, linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v3] fs/sync.c: sync_file_range(2) may use WB_SYNC_ALL writeback Date: Thu, 11 Apr 2019 20:00:42 +0300 Message-Id: <20190411170042.16111-1-amir73il@gmail.com> X-Mailer: git-send-email 2.17.1 Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Commit 23d0127096cb ("fs/sync.c: make sync_file_range(2) use WB_SYNC_NONE writeback") claims that sync_file_range(2) syscall was "created for userspace to be able to issue background writeout and so waiting for in-flight IO is undesirable there" and changes the writeback (back) to WB_SYNC_NONE. This claim is only partially true. It is true for users that use the flag SYNC_FILE_RANGE_WRITE by itself, as does PostgreSQL, the user that was the reason for changing to WB_SYNC_NONE writeback. However, that claim is not true for users that use that flag combination SYNC_FILE_RANGE_{WAIT_BEFORE|WRITE|_WAIT_AFTER}. Those users explicitly requested to wait for in-flight IO as well as to writeback of dirty pages. Re-brand that flag combination as SYNC_FILE_RANGE_WRITE_AND_WAIT and use the helper filemap_write_and_wait_range(), that uses WB_SYNC_ALL writeback, to perform the full range sync request. Fixes: 23d0127096cb ("fs/sync.c: make sync_file_range(2) use WB_SYNC_NONE") Acked-by: Jan Kara Signed-off-by: Amir Goldstein --- Andrew, Oops found a braino in my patch. Here is v3. You may find the discussion on V1 here: https://lore.kernel.org/lkml/20190409114922.30095-1-amir73il@gmail.com/ Thanks, Amir. Changes since v2: - Return after filemap_write_and_wait_range() Changes since v1: - Remove non-guaranties of the API from commit message - Added ACK by Jan fs/sync.c | 24 +++++++++++++++++------- include/uapi/linux/fs.h | 3 +++ 2 files changed, 20 insertions(+), 7 deletions(-) diff --git a/fs/sync.c b/fs/sync.c index b54e0541ad89..3a923652d720 100644 --- a/fs/sync.c +++ b/fs/sync.c @@ -18,8 +18,8 @@ #include #include "internal.h" -#define VALID_FLAGS (SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE| \ - SYNC_FILE_RANGE_WAIT_AFTER) +#define VALID_FLAGS (SYNC_FILE_RANGE_WRITE | SYNC_FILE_RANGE_WRITE_AND_WAIT | \ + SYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WAIT_AFTER) /* * Do the filesystem syncing work. For simple filesystems @@ -235,9 +235,9 @@ SYSCALL_DEFINE1(fdatasync, unsigned int, fd) } /* - * sys_sync_file_range() permits finely controlled syncing over a segment of + * ksys_sync_file_range() permits finely controlled syncing over a segment of * a file in the range offset .. (offset+nbytes-1) inclusive. If nbytes is - * zero then sys_sync_file_range() will operate from offset out to EOF. + * zero then ksys_sync_file_range() will operate from offset out to EOF. * * The flag bits are: * @@ -254,7 +254,7 @@ SYSCALL_DEFINE1(fdatasync, unsigned int, fd) * Useful combinations of the flag bits are: * * SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE: ensures that all pages - * in the range which were dirty on entry to sys_sync_file_range() are placed + * in the range which were dirty on entry to ksys_sync_file_range() are placed * under writeout. This is a start-write-for-data-integrity operation. * * SYNC_FILE_RANGE_WRITE: start writeout of all dirty pages in the range which @@ -266,10 +266,13 @@ SYSCALL_DEFINE1(fdatasync, unsigned int, fd) * earlier SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE operation to wait * for that operation to complete and to return the result. * - * SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE|SYNC_FILE_RANGE_WAIT_AFTER: + * SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE|SYNC_FILE_RANGE_WAIT_AFTER + * (a.k.a. SYNC_FILE_RANGE_WRITE_AND_WAIT): * a traditional sync() operation. This is a write-for-data-integrity operation * which will ensure that all pages in the range which were dirty on entry to - * sys_sync_file_range() are committed to disk. + * ksys_sync_file_range() are written to disk. It should be noted that disk + * caches are not flushed by this call, so there are no guarantees here that the + * data will be available on disk after a crash. * * * SYNC_FILE_RANGE_WAIT_BEFORE and SYNC_FILE_RANGE_WAIT_AFTER will detect any @@ -338,6 +341,13 @@ int ksys_sync_file_range(int fd, loff_t offset, loff_t nbytes, mapping = f.file->f_mapping; ret = 0; + if ((flags & SYNC_FILE_RANGE_WRITE_AND_WAIT) == + SYNC_FILE_RANGE_WRITE_AND_WAIT) { + /* Unlike SYNC_FILE_RANGE_WRITE alone uses WB_SYNC_ALL */ + ret = filemap_write_and_wait_range(mapping, offset, endbyte); + goto out_put; + } + if (flags & SYNC_FILE_RANGE_WAIT_BEFORE) { ret = file_fdatawait_range(f.file, offset, endbyte); if (ret < 0) diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h index 121e82ce296b..59c71fa8c553 100644 --- a/include/uapi/linux/fs.h +++ b/include/uapi/linux/fs.h @@ -320,6 +320,9 @@ struct fscrypt_key { #define SYNC_FILE_RANGE_WAIT_BEFORE 1 #define SYNC_FILE_RANGE_WRITE 2 #define SYNC_FILE_RANGE_WAIT_AFTER 4 +#define SYNC_FILE_RANGE_WRITE_AND_WAIT (SYNC_FILE_RANGE_WRITE | \ + SYNC_FILE_RANGE_WAIT_BEFORE | \ + SYNC_FILE_RANGE_WAIT_AFTER) /* * Flags for preadv2/pwritev2: