From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-f171.google.com ([209.85.166.171]:52504 "EHLO mail-it1-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725935AbeIXOXC (ORCPT ); Mon, 24 Sep 2018 10:23:02 -0400 Received: by mail-it1-f171.google.com with SMTP id h3-v6so9402889ita.2 for ; Mon, 24 Sep 2018 01:22:08 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <87worbs4ju.fsf@thinkpad.rath.org> References: <87worbs4ju.fsf@thinkpad.rath.org> From: Miklos Szeredi Date: Mon, 24 Sep 2018 10:22:07 +0200 Message-ID: Subject: Re: [fuse] What happens with dirty pages on NOTIFY_INVAL_INODE? To: fuse-devel , linux-fsdevel , Miklos Szeredi Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Sep 24, 2018 at 10:06 AM, Nikolaus Rath wrote: > Hi, > > What happens with dirty pages when a (writeback-cache enabled) FUSE > filesystem sends a NOTIFY_INVAL_INODE request? Are they dropped? > flushed? Haven't tried, but AFAICS it flushes dirty pages and waits on writeback for these. However, it doesn't wait on already queued writes. So it's a bit of a mess at the moment. > > To me neither behaviour seems correct... What would be the correct operation be if neither flushing not dropping them is correct? Thanks, Miklos