From: Petr Vorel <pvorel@suse.cz>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>,
lkp@intel.com, linux-kernel@vger.kernel.org,
AnonymeMeow <anonymemeow@gmail.com>,
linux-fsdevel@vger.kernel.org, oe-lkp@lists.linux.dev,
ltp@lists.linux.it
Subject: Re: [LTP] [linus:master] [fanotify] 82c6dd2047: ltp.fanotify21.fail
Date: Tue, 25 Aug 2026 12:39:48 +0200 [thread overview]
Message-ID: <20260825103948.GA57544@pevik> (raw)
In-Reply-To: <akNRvmJdCKALZbo6@xsang-OptiPlex-9020>
Hi Jan, all,
> hi, Jan Kara,
> On Mon, Jun 29, 2026 at 11:36:25AM +0200, Jan Kara wrote:
> > On Mon 29-06-26 16:45:58, kernel test robot wrote:
> > > kernel test robot noticed "ltp.fanotify21.fail" on:
> > > commit: 82c6dd20479bb6a9625e1d63a650c3be8865e2db ("fanotify: allow reporting pidfds for reaped tasks")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > FWIW this is expected failure. Patch to fix fanotify21 to accept success
> > in this test was submitted to LTP.
Jan, thanks a lot for a ping, I completely forgot on the rest of the patchset,
these 4 commits merged now.
> thanks a lot for information!
Oliver, FYI 7.2 specific fix:
https://github.com/linux-test-project/ltp/commit/a851461ea951622a973980510d031bb6b24a5541
The rest are enhancements.
Kind regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
lkp@intel.com, linux-kernel@vger.kernel.org,
AnonymeMeow <anonymemeow@gmail.com>,
oe-lkp@lists.linux.dev, linux-fsdevel@vger.kernel.org,
ltp@lists.linux.it
Subject: Re: [LTP] [linus:master] [fanotify] 82c6dd2047: ltp.fanotify21.fail
Date: Tue, 25 Aug 2026 12:39:48 +0200 [thread overview]
Message-ID: <20260825103948.GA57544@pevik> (raw)
In-Reply-To: <akNRvmJdCKALZbo6@xsang-OptiPlex-9020>
Hi Jan, all,
> hi, Jan Kara,
> On Mon, Jun 29, 2026 at 11:36:25AM +0200, Jan Kara wrote:
> > On Mon 29-06-26 16:45:58, kernel test robot wrote:
> > > kernel test robot noticed "ltp.fanotify21.fail" on:
> > > commit: 82c6dd20479bb6a9625e1d63a650c3be8865e2db ("fanotify: allow reporting pidfds for reaped tasks")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > FWIW this is expected failure. Patch to fix fanotify21 to accept success
> > in this test was submitted to LTP.
Jan, thanks a lot for a ping, I completely forgot on the rest of the patchset,
these 4 commits merged now.
> thanks a lot for information!
Oliver, FYI 7.2 specific fix:
https://github.com/linux-test-project/ltp/commit/a851461ea951622a973980510d031bb6b24a5541
The rest are enhancements.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-25 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 8:45 [linus:master] [fanotify] 82c6dd2047: ltp.fanotify21.fail kernel test robot
2026-06-29 8:45 ` [LTP] " kernel test robot
2026-06-29 9:36 ` Jan Kara
2026-06-29 9:36 ` [LTP] " Jan Kara
2026-06-30 5:18 ` Oliver Sang
2026-06-30 5:18 ` [LTP] " Oliver Sang
2026-08-25 10:39 ` Petr Vorel [this message]
2026-08-25 10:39 ` 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=20260825103948.GA57544@pevik \
--to=pvorel@suse.cz \
--cc=anonymemeow@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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.