From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
Alex Williamson <alex.williamson@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/3] Fix for huge faults regression
Date: Mon, 3 Feb 2025 23:32:02 +0100 [thread overview]
Message-ID: <20250203223205.861346-1-amir73il@gmail.com> (raw)
Christian,
I thought these fixes could go through your tree, because they are
mostly vfs/file related.
Hoping that Jan could provide an ACK.
The two Fix patches have been tested by Alex together and each one
independently.
I also verified that they pass the LTP inoityf/fanotify tests.
Thanks,
Amir.
Amir Goldstein (3):
fsnotify: use accessor to set FMODE_NONOTIFY_*
fsnotify: disable notification by default for all pseudo files
fsnotify: disable pre-content and permission events by default
drivers/tty/pty.c | 2 +-
fs/file_table.c | 16 ++++++++++++++++
fs/notify/fsnotify.c | 18 ++++++++++++------
fs/open.c | 11 ++++++-----
fs/pipe.c | 6 ++++++
include/linux/fs.h | 9 ++++++++-
include/linux/fsnotify.h | 4 ++--
net/socket.c | 5 +++++
8 files changed, 56 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2025-02-03 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 22:32 Amir Goldstein [this message]
2025-02-03 22:32 ` [PATCH 1/3] fsnotify: use accessor to set FMODE_NONOTIFY_* Amir Goldstein
2025-02-04 10:43 ` Christian Brauner
2025-02-04 10:58 ` Amir Goldstein
2025-02-05 16:52 ` Jan Kara
2025-02-03 22:32 ` [PATCH 2/3] fsnotify: disable notification by default for all pseudo files Amir Goldstein
2025-02-05 16:52 ` Jan Kara
2025-02-03 22:32 ` [PATCH 3/3] fsnotify: disable pre-content and permission events by default Amir Goldstein
2025-02-05 16:59 ` Jan Kara
2025-02-05 22:20 ` Amir Goldstein
2025-02-05 13:12 ` [PATCH 0/3] Fix for huge faults regression Christian Brauner
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=20250203223205.861346-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.