archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <>
To: fuse-devel <>,
	linux-fsdevel <>,
	Miklos Szeredi <>
Subject: Re: [fuse] What happens with dirty pages on NOTIFY_INVAL_INODE?
Date: Mon, 24 Sep 2018 10:22:07 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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?


  reply	other threads:[~2018-09-24 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  8:06 [fuse] What happens with dirty pages on NOTIFY_INVAL_INODE? Nikolaus Rath
2018-09-24  8:22 ` Miklos Szeredi [this message]
2018-09-24  8:43   ` [fuse-devel] " Nikolaus Rath
2018-09-24 13:38     ` Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).