From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Gabriel Krisman Bertazi <krisman@collabora.com>,
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>,
Cyril Hrubis <chrubis@suse.cz>,
Richard Palethorpe <rpalethorpe@suse.com>
Subject: Re: [LTP] [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Mon, 20 Dec 2021 19:07:35 +0100 [thread overview]
Message-ID: <YcDGZ+eNcQ5fPsmN@pevik> (raw)
In-Reply-To: <CAOQ4uxgg6BvUtcaD4stDv7meS0it-0-iDWNiz_-=SRN_tvgzYQ@mail.gmail.com>
Hi Amir,
[ Cc Cyril and Richie ]
> On Wed, Nov 24, 2021 at 12:40 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi all,
> > <snip>
> > > > Hi Amir,
> > > > I have pushed v4 to :
> > > > https://gitlab.collabora.com/krisman/ltp.git -b fan-fs-error_v4
> > > FYI I've rebased it on my fix 3b2ea2e00 ("configure.ac: Add struct
> > > fanotify_event_info_pidfd check")
> > > https://github.com/linux-test-project/ltp.git -b gertazi/fanotify21.v4.fixes
> > FYI I removed branch from official LTP repository and put it to my fork
> > https://github.com/pevik/ltp.git -b fan-fs-error_v4.fixes
> Hi Petr,
> Are you waiting with this merge for after release of v5.16?
> or is it just waiting behind other work?
Yes. Thanks for this input, we're just discussing our policy about tests for new
(kernel) release functionality. First we agreed to wait [1] (due problems
described in [2]), Richie is suggesting to merge earlier [2], although Cyril
had doubts it's worth of the work [3].
Kind regards,
Petr
> Just asking out of curiosity.
> I've based my tests for fan_rename (queued for v5.17) on top of your branch.
> Thanks,
> Amir.
[1] https://lore.kernel.org/ltp/20211210134556.26091-1-pvorel@suse.cz/
[2] https://lore.kernel.org/ltp/87lf0ffw1y.fsf@suse.de/
[3] https://lore.kernel.org/ltp/Ybc5QJSZM3YIji70@yuki/
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: kernel@collabora.com, Khazhismel Kumykov <khazhy@google.com>,
Matthew Bobrowski <repnop@google.com>, Jan Kara <jack@suse.com>,
Ext4 <linux-ext4@vger.kernel.org>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
Richard Palethorpe <rpalethorpe@suse.com>,
LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Mon, 20 Dec 2021 19:07:35 +0100 [thread overview]
Message-ID: <YcDGZ+eNcQ5fPsmN@pevik> (raw)
In-Reply-To: <CAOQ4uxgg6BvUtcaD4stDv7meS0it-0-iDWNiz_-=SRN_tvgzYQ@mail.gmail.com>
Hi Amir,
[ Cc Cyril and Richie ]
> On Wed, Nov 24, 2021 at 12:40 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi all,
> > <snip>
> > > > Hi Amir,
> > > > I have pushed v4 to :
> > > > https://gitlab.collabora.com/krisman/ltp.git -b fan-fs-error_v4
> > > FYI I've rebased it on my fix 3b2ea2e00 ("configure.ac: Add struct
> > > fanotify_event_info_pidfd check")
> > > https://github.com/linux-test-project/ltp.git -b gertazi/fanotify21.v4.fixes
> > FYI I removed branch from official LTP repository and put it to my fork
> > https://github.com/pevik/ltp.git -b fan-fs-error_v4.fixes
> Hi Petr,
> Are you waiting with this merge for after release of v5.16?
> or is it just waiting behind other work?
Yes. Thanks for this input, we're just discussing our policy about tests for new
(kernel) release functionality. First we agreed to wait [1] (due problems
described in [2]), Richie is suggesting to merge earlier [2], although Cyril
had doubts it's worth of the work [3].
Kind regards,
Petr
> Just asking out of curiosity.
> I've based my tests for fan_rename (queued for v5.17) on top of your branch.
> Thanks,
> Amir.
[1] https://lore.kernel.org/ltp/20211210134556.26091-1-pvorel@suse.cz/
[2] https://lore.kernel.org/ltp/87lf0ffw1y.fsf@suse.de/
[3] https://lore.kernel.org/ltp/Ybc5QJSZM3YIji70@yuki/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-12-20 18:07 UTC|newest]
Thread overview: 58+ 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 ` [LTP] " 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 ` [LTP] " 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 ` [LTP] " 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 ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 4/9] syscalls/fanotify22: Validate the generic error info Gabriel Krisman Bertazi
2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi
2021-11-19 5:38 ` Amir Goldstein
2021-11-19 5:38 ` [LTP] " Amir Goldstein
2021-11-19 19:29 ` Petr Vorel
2021-11-19 19:29 ` [LTP] " Petr Vorel
2021-11-19 22:39 ` Petr Vorel
2021-11-19 22:39 ` [LTP] " 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 ` [LTP] " 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 ` [LTP] " 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 ` [LTP] " 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 ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 9/9] syscalls/fanotify22: Test capture of multiple errors Gabriel Krisman Bertazi
2021-11-18 23:57 ` [LTP] " 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 5:48 ` [LTP] " Amir Goldstein
2021-11-19 19:29 ` Gabriel Krisman Bertazi
2021-11-19 19:29 ` [LTP] " Gabriel Krisman Bertazi
2021-11-20 10:43 ` Amir Goldstein
2021-11-20 10:43 ` [LTP] " Amir Goldstein
2021-11-22 7:47 ` Petr Vorel
2021-11-22 7:47 ` [LTP] " Petr Vorel
2021-11-22 17:35 ` Gabriel Krisman Bertazi
2021-11-22 17:35 ` [LTP] " Gabriel Krisman Bertazi
2021-11-22 21:09 ` Petr Vorel
2021-11-22 21:09 ` [LTP] " Petr Vorel
2021-11-24 10:39 ` Petr Vorel
2021-11-24 10:39 ` Petr Vorel
2021-12-20 11:48 ` Amir Goldstein
2021-12-20 11:48 ` Amir Goldstein
2021-12-20 18:07 ` Petr Vorel [this message]
2021-12-20 18:07 ` Petr Vorel
2022-01-10 15:16 ` Petr Vorel
2022-01-10 15:16 ` [LTP] " Petr Vorel
2022-02-02 13:49 ` Amir Goldstein
2022-02-02 13:49 ` [LTP] " Amir Goldstein
2022-02-02 14:10 ` Jan Stancek
2022-02-02 14:10 ` Jan Stancek
2022-02-02 16:45 ` Gabriel Krisman Bertazi
2022-02-02 16:45 ` Gabriel Krisman Bertazi
2022-02-02 14:22 ` Petr Vorel
2022-02-02 14:22 ` [LTP] " Petr Vorel
2022-02-02 16:13 ` Cyril Hrubis
2022-02-02 16:13 ` Cyril Hrubis
2022-02-02 16:57 ` Petr Vorel
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=YcDGZ+eNcQ5fPsmN@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=chrubis@suse.cz \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=repnop@google.com \
--cc=rpalethorpe@suse.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 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.