From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Ivan Delalande <colona@arista.com>, Jan Kara <jack@suse.cz>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/inotify: New test for IN_DELETE regression
Date: Thu, 3 Feb 2022 08:59:35 +0100 [thread overview]
Message-ID: <YfuLZxav/jI35QQF@pevik> (raw)
In-Reply-To: <20220203061222.625948-1-amir73il@gmail.com>
Hi Amir,
thanks for this test.
> Check that files cannot be opened after IN_DELETE was reported
> on them.
> This test is based on the reproducer provided by Ivan Delalande
> for a regression reported in kernel v5.13:
> https://lore.kernel.org/linux-fsdevel/YeNyzoDM5hP5LtGW@visor/
> Reported-by: Ivan Delalande <colona@arista.com>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> Hi Petr,
> The fix for this regression was applied to stable kernels
> 5.4.y, 5.10.y, 5.15.y, 5.16.y.
> The mentioned git tag is only the upstream commit.
> Feel free to add the stable git tags if you think they are needed.
FYI we don't track stable git commits which are normally backported
(vast majority of commits), we track only stable git specific fixes,
i.e.:
* c4a23c852e80 ("io_uring: Fix current->fs handling in io_sq_wq_submit_work()")
"No upstream commit, this is a fix to a stable 5.4 specific backport."
* cac68d12c531 ("io_uring: grab ->fs as part of async offload")
[ Upstream commits 9392a27d88b9 and ff002b30181d ]
Mentioned at note:
https://github.com/linux-test-project/ltp/wiki/C-Test-API#138-test-tags
The reason is that user can search simple backports himself.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-02-03 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 6:12 [LTP] [PATCH] syscalls/inotify: New test for IN_DELETE regression Amir Goldstein
2022-02-03 7:59 ` Petr Vorel [this message]
2022-02-07 9:53 ` Petr Vorel
2022-02-07 13:25 ` Amir Goldstein
2022-02-07 13:35 ` Petr Vorel
2022-02-07 14:46 ` Cyril Hrubis
2022-02-07 21:18 ` 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=YfuLZxav/jI35QQF@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=colona@arista.com \
--cc=jack@suse.cz \
--cc=ltp@lists.linux.it \
/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