From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org,
Hungyu Lin <dennylin0707@gmail.com>,
jack@suse.cz, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] inotify13: check rename cookie pairing after adjacent moves
Date: Wed, 4 Nov 2026 17:43:48 +0100 [thread overview]
Message-ID: <20261104164348.GA396365@pevik> (raw)
In-Reply-To: <20261030174855.GA53338@pevik>
Hi Hungyu Lin, Amir,
Given this is a test for bug from v2.6.31 I kept it in runtest/syscalls and
merged, thank you!
I suppose the fix is [PATCH v2] inotify: do not coalesce rename events [1].
Although Jan stated "added to my tree" [2] I haven't found it in his for_next
branch [3]. Please update the hash in the test or Cc me once it's merged.
Kind regards,
Petr
[1] https://lore.kernel.org/lkml/20261027192027.8617-1-dennylin0707@gmail.com/
[2] https://lore.kernel.org/lkml/u6fltejwlekpknwpxzy6pefif7ld3dhwvzqqalbzmtwtzjjaj2@hsulwhevxfds/
[3] https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git/log/?h=for_next
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org,
Hungyu Lin <dennylin0707@gmail.com>,
jack@suse.cz, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] inotify13: check rename cookie pairing after adjacent moves
Date: Wed, 4 Nov 2026 17:43:48 +0100 [thread overview]
Message-ID: <20261104164348.GA396365@pevik> (raw)
In-Reply-To: <20261030174855.GA53338@pevik>
Hi Hungyu Lin, Amir,
Given this is a test for bug from v2.6.31 I kept it in runtest/syscalls and
merged, thank you!
I suppose the fix is [PATCH v2] inotify: do not coalesce rename events [1].
Although Jan stated "added to my tree" [2] I haven't found it in his for_next
branch [3]. Please update the hash in the test or Cc me once it's merged.
Kind regards,
Petr
[1] https://lore.kernel.org/lkml/20261027192027.8617-1-dennylin0707@gmail.com/
[2] https://lore.kernel.org/lkml/u6fltejwlekpknwpxzy6pefif7ld3dhwvzqqalbzmtwtzjjaj2@hsulwhevxfds/
[3] https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git/log/?h=for_next
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-11-04 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 21:07 [LTP] [PATCH v4] inotify13: check rename cookie pairing after adjacent moves Hungyu Lin
2026-10-29 21:07 ` Hungyu Lin
2026-10-30 0:31 ` [LTP] " linuxtestproject.agent
2026-10-30 9:20 ` [LTP] [PATCH v4] " Amir Goldstein
2026-10-30 9:20 ` Amir Goldstein
2026-10-30 17:06 ` [LTP] " Petr Vorel
2026-10-30 17:06 ` Petr Vorel
2026-10-30 17:30 ` Amir Goldstein
2026-10-30 17:30 ` Amir Goldstein
2026-10-30 17:48 ` Petr Vorel
2026-10-30 17:48 ` Petr Vorel
2026-11-04 16:43 ` Petr Vorel [this message]
2026-11-04 16:43 ` 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=20261104164348.GA396365@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=dennylin0707@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.