From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: Amir Goldstein <amir73il@gmail.com>, Petr Vorel <pvorel@suse.cz>,
kernel@collabora.com, Khazhismel Kumykov <khazhy@google.com>,
Matthew Bobrowski <repnop@google.com>, Jan Kara <jack@suse.com>,
Ext4 <linux-ext4@vger.kernel.org>, LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Wed, 02 Feb 2022 11:45:24 -0500 [thread overview]
Message-ID: <875ypxgqu3.fsf@collabora.com> (raw)
In-Reply-To: <CAASaF6xQG691q9JxiEF5HgqCNfGd1FHhwEX5TG_WpW3rHpBFKQ@mail.gmail.com> (Jan Stancek's message of "Wed, 2 Feb 2022 15:10:26 +0100")
Jan Stancek <jstancek@redhat.com> writes:
> On Wed, Feb 2, 2022 at 2:49 PM Amir Goldstein <amir73il@gmail.com> wrote:
>> Guys,
>>
>> Looks like we have a regression.
>
> agreed, "abort" option stopped working:
> https://gitlab.com/cki-project/kernel-tests/-/issues/945
>
> Lukas pointed out this patch that didn't make it in yet:
> https://lkml.org/lkml/2021/12/21/384
> This should be new version:
> https://lore.kernel.org/linux-ext4/YcSYvk5DdGjjB9q%2F@mit.edu/T/#t
I gave this patch a try and verified it fixes the test case regression.
Let me ask Ted to make sure it is merged for the 5.17 release.
Thanks,
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2022-02-02 16:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 23:57 [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 1/9] syscalls: fanotify: Add macro to require specific mark types Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 2/9] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 3/9] syscalls/fanotify22: Introduce FAN_FS_ERROR test Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 4/9] syscalls/fanotify22: Validate the generic error info Gabriel Krisman Bertazi
2021-11-19 5:38 ` Amir Goldstein
2021-11-19 19:29 ` Petr Vorel
2021-11-19 22:39 ` Petr Vorel
2021-11-18 23:57 ` [PATCH v4 5/9] syscalls/fanotify22: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 6/9] syscalls/fanotify22: Support submission of debugfs commands Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 7/9] syscalls/fanotify22: Create a corrupted file Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 8/9] syscalls/fanotify22: Test file event with broken inode Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 9/9] syscalls/fanotify22: Test capture of multiple errors Gabriel Krisman Bertazi
2021-11-19 5:48 ` [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Amir Goldstein
2021-11-19 19:29 ` Gabriel Krisman Bertazi
2021-11-20 10:43 ` Amir Goldstein
2021-11-22 7:47 ` Petr Vorel
2021-11-22 17:35 ` Gabriel Krisman Bertazi
2021-11-22 21:09 ` Petr Vorel
2021-11-24 10:39 ` [LTP] " Petr Vorel
2021-12-20 11:48 ` Amir Goldstein
2021-12-20 18:07 ` Petr Vorel
2022-01-10 15:16 ` Petr Vorel
2022-02-02 13:49 ` Amir Goldstein
2022-02-02 14:10 ` [LTP] " Jan Stancek
2022-02-02 16:45 ` Gabriel Krisman Bertazi [this message]
2022-02-02 14:22 ` Petr Vorel
2022-02-02 16:13 ` [LTP] " Cyril Hrubis
2022-02-02 16:57 ` Petr Vorel
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=875ypxgqu3.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.com \
--cc=jstancek@redhat.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=repnop@google.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;
as well as URLs for NNTP newsgroup(s).