From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amir Goldstein Subject: Re: sync filesystem of overlayfs Date: Mon, 27 Nov 2017 19:51:45 +0200 Message-ID: References: <5862C310-F8B9-40AF-826D-BE867CCDA519@mykernel.net> <771732B7-80A0-4011-BC98-9A40375A8858@mykernel.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-yw0-f181.google.com ([209.85.161.181]:40984 "EHLO mail-yw0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752746AbdK0Rvr (ORCPT ); Mon, 27 Nov 2017 12:51:47 -0500 Received: by mail-yw0-f181.google.com with SMTP id k3so12173039ywk.8 for ; Mon, 27 Nov 2017 09:51:46 -0800 (PST) In-Reply-To: Sender: linux-unionfs-owner@vger.kernel.org List-Id: linux-unionfs@vger.kernel.org To: cgxu Cc: overlayfs , suyue@meili-inc.com On Mon, Nov 27, 2017 at 5:30 PM, cgxu wrote: > Hi Amir > > Per the previous discussion, my opinion is calling __sync_filesystem() in= ovl_sync_fs() > would be better for current stage. If we pick up overlayfs=E2=80=99s dirt= y inodes we may need to > involve writeback and cgroup logics in overlayfs and put all things into = sync_fs seems > quite heavy and complex. If you agree I=E2=80=99ll make new patch for rev= iew. > That sounds good to me. Thanks, Amir.