From: Jan Kara <jack@suse.cz>
To: Christian Brauner <brauner@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
James Clark <james.clark@arm.com>,
linux-nfs@vger.kernel.org, NeilBrown <neilb@suse.de>,
Al Viro <viro@ZenIV.linux.org.uk>,
ltp@lists.linux.it, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2 v3] fsnotify: Generate FS_CREATE event before FS_OPEN
Date: Mon, 17 Jun 2024 18:22:59 +0200 [thread overview]
Message-ID: <20240617161828.6718-1-jack@suse.cz> (raw)
Hello,
this is a third revision of the series Neil started making sure FS_CREATE event
is generated before FS_OPEN event even for filesystems using atomic_open.
Changes since v2:
* Don't generate FS_OPEN events for O_PATH fd opens
* Move generation of FS_OPEN event for atomic_open() into a more logical place
Previous version:
v2: https://lore.kernel.org/all/171817619547.14261.975798725161704336@noble.neil.brown.name/
Honza
next reply other threads:[~2024-06-17 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 16:22 Jan Kara [this message]
2024-06-17 16:23 ` [PATCH 1/2] fsnotify: Do not generate events for O_PATH file descriptors Jan Kara
2024-06-17 17:10 ` Amir Goldstein
2024-06-18 14:28 ` Christian Brauner
2024-06-19 15:24 ` Jan Kara
2024-06-17 16:23 ` [PATCH 2/2] vfs: generate FS_CREATE before FS_OPEN when ->atomic_open used Jan Kara
2024-06-17 17:12 ` Amir Goldstein
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=20240617161828.6718-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=james.clark@arm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=neilb@suse.de \
--cc=viro@ZenIV.linux.org.uk \
/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