From: Paul Lawrence <paullawrence@google.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: Regression: File truncate inotify behavior change
Date: Sat, 17 Feb 2024 10:53:31 -0800 [thread overview]
Message-ID: <CAL=UVf5FKEqTrHKnKv5c5iQmZ6WOfSw2YwTmnOU-Uv8WWiCyYw@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxgR1Z9LXAiRwgQ6h9avBphYttLeQS2JFWtzQr6ck6AiKw@mail.gmail.com>
OK, that makes sense. I checked that I still get a modify even if I
don't write to the file. It's hard to imagine an actual application
(not a test app) depending on this exact ordering. I will change our
CTS test to be more tolerant.
Thanks for the quick response,
Paul
prev parent reply other threads:[~2024-02-17 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 19:53 Regression: File truncate inotify behavior change Paul Lawrence
[not found] ` <CAOQ4uxgR1Z9LXAiRwgQ6h9avBphYttLeQS2JFWtzQr6ck6AiKw@mail.gmail.com>
2024-02-17 18:53 ` Paul Lawrence [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL=UVf5FKEqTrHKnKv5c5iQmZ6WOfSw2YwTmnOU-Uv8WWiCyYw@mail.gmail.com' \
--to=paullawrence@google.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).