From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-f66.google.com ([209.85.161.66]:36357 "EHLO mail-yw1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726790AbfA1WOM (ORCPT ); Mon, 28 Jan 2019 17:14:12 -0500 Received: by mail-yw1-f66.google.com with SMTP id i73so7412133ywg.3 for ; Mon, 28 Jan 2019 14:14:12 -0800 (PST) MIME-Version: 1.0 References: <20190128192207.GA10240@redhat.com> In-Reply-To: From: Amir Goldstein Date: Tue, 29 Jan 2019 00:14:00 +0200 Message-ID: Subject: Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap Content-Type: text/plain; charset="UTF-8" Sender: linux-unionfs-owner@vger.kernel.org To: Miklos Szeredi Cc: Vivek Goyal , cgxu519 , overlayfs List-ID: On Mon, Jan 28, 2019 at 11:22 PM Miklos Szeredi wrote: > > On Mon, Jan 28, 2019 at 10:17 PM Miklos Szeredi wrote: > > > Trying to put some code together... > > Very rudimentary patch attached. It doens't do direct IO yet, but > demonstrates what I meant about achoring the upper file in the inode. > Code looks good, but blows up on xfstests, so I'll wait for a baked patch before testing. > Also found the trick to actually make writeback work: > super_setup_bdi() call in fill_super... > Cool, but when adding only setup_bdi() this to my code, I still don't see any writeback. No writeback observed with your patch as well. Speaking of which, did you read the warning sign above simple_write_end()? Aren't you missing the mark_inode_dirty() call? Thanks, Amir.