From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:50693 "EHLO
        out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1726074AbeIXOHG (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Mon, 24 Sep 2018 10:07:06 -0400
From: Nikolaus Rath <Nikolaus@rath.org>
To: fuse-devel <fuse-devel@lists.sourceforge.net>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        Miklos Szeredi <mszeredi@redhat.com>
Subject: [fuse] What happens with dirty pages on NOTIFY_INVAL_INODE?
Date: Mon, 24 Sep 2018 09:06:13 +0100
Message-ID: <87worbs4ju.fsf@thinkpad.rath.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Hi,

What happens with dirty pages when a (writeback-cache enabled) FUSE
filesystem sends a NOTIFY_INVAL_INODE request? Are they dropped?
flushed?

To me neither behaviour seems correct...=20


Best,
-Nikolaus

--=20
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2=
=AB