From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Ajay Kaher <ajay.kaher@broadcom.com>,
gregkh@linuxfoundation.org, chuck.lever@oracle.com,
krisman@collabora.com, patches@lists.linux.dev,
sashal@kernel.org, stable@vger.kernel.org,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
tytso@mit.edu, alexey.makhalov@broadcom.com,
vasavi.sirnapalli@broadcom.com, florian.fainelli@broadcom.com
Subject: Re: [PATCH 5.10 387/770] fanotify: Allow users to request FAN_FS_ERROR events
Date: Tue, 23 Jul 2024 12:47:04 +0200 [thread overview]
Message-ID: <20240723104704.cqhqkkvslojg77x7@quack3> (raw)
In-Reply-To: <CAOQ4uxjGrPbq8=znBSV8i79Kj2Or4p5O5BZ0+RL1oXbxxNu3rw@mail.gmail.com>
On Tue 23-07-24 13:13:41, Amir Goldstein wrote:
> On Tue, Jul 23, 2024 at 12:29 PM Jan Kara <jack@suse.cz> wrote:
> >
> > On Tue 23-07-24 12:36:27, Ajay Kaher wrote:
> > > > [ Upstream commit 9709bd548f11a092d124698118013f66e1740f9b ]
> > > >
> > > > Wire up the FAN_FS_ERROR event in the fanotify_mark syscall, allowing
> > > > user space to request the monitoring of FAN_FS_ERROR events.
> > > >
> > > > These events are limited to filesystem marks, so check it is the
> > > > case in the syscall handler.
> > >
> > > Greg,
> > >
> > > Without 9709bd548f11 in v5.10.y skips LTP fanotify22 test case, as:
> > > fanotify22.c:312: TCONF: FAN_FS_ERROR not supported in kernel
> > >
> > > With 9709bd548f11 in v5.10.220, LTP fanotify22 is failing because of
> > > timeout as no notification. To fix need to merge following two upstream
> > > commit to v5.10:
> > >
> > > 124e7c61deb27d758df5ec0521c36cf08d417f7a:
> > > 0001-ext4_fix_error_code_saved_on_super_block_during_file_system.patch
> > > https://lore.kernel.org/stable/1721717240-8786-1-git-send-email-ajay.kaher@broadcom.com/T/#mf76930487697d8c1383ed5d21678fe504e8e2305
> > >
> > > 9a089b21f79b47eed240d4da7ea0d049de7c9b4d:
> > > 0001-ext4_Send_notifications_on_error.patch
> > > Link: https://lore.kernel.org/stable/1721717240-8786-1-git-send-email-ajay.kaher@broadcom.com/T/#md1be98e0ecafe4f92d7b61c048e15bcf286cbd53
> >
> > I know Chuck has been backporting the huge pile of fsnotify changes for
> > stable and he was running LTP so I'm a bit curious if he saw the fanotify22
> > failure as well. The reason for the test failure seems to be that the
> > combination of features now present in stable has never been upstream which
> > confuses the test. As such I'm not sure if backporting more features to
> > stable is warranted just to fix a broken LTP test... But given the huge
> > pile Chuck has backported already I'm not strongly opposed to backporting a
> > few more, there's just a question where does this stop :)
>
> I'm not sure is it exactly "more features". The fanotify patches and
> ext4 patches that use them where merges as a feature together.
>
> IOW, FAN_FS_ERROR was merged with support for a single fs (ext4)
> it would be weird to backport the feature with support for zero fs.
> Also, 5.15.y already has the ext4 patches - not sure why 5.10.y didn't get them.
I forgot 5.15.y got all the patches. Ok, then pushing them to 5.10.y makes
sense as well.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-07-23 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618123422.213844892@linuxfoundation.org>
2024-07-23 7:06 ` [PATCH 5.10 387/770] fanotify: Allow users to request FAN_FS_ERROR events Ajay Kaher
2024-07-23 9:20 ` Amir Goldstein
2024-07-23 13:47 ` Chuck Lever III
2024-07-24 6:52 ` Amir Goldstein
2024-07-23 14:34 ` Gabriel Krisman Bertazi
2024-07-23 15:57 ` Chuck Lever III
2024-07-23 21:42 ` [PATCH v5.15.y] Revert "fanotify: Allow users to request FAN_FS_ERROR events" cel
2024-07-23 23:24 ` Gabriel Krisman Bertazi
2024-07-24 6:42 ` Amir Goldstein
2024-07-23 9:29 ` [PATCH 5.10 387/770] fanotify: Allow users to request FAN_FS_ERROR events Jan Kara
2024-07-23 10:13 ` Amir Goldstein
2024-07-23 10:47 ` Jan Kara [this message]
2024-07-23 13:44 ` Chuck Lever III
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=20240723104704.cqhqkkvslojg77x7@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=amir73il@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vasavi.sirnapalli@broadcom.com \
/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