Applying with these fixes on my side: - moved 5/5 "ms/eventfs: Initialize ei->children and ei->list in init_ei()" in front of 3/5, no other change.
On Thu, 12 Nov 2026 02:07:52 +0200, Eva Kurchatova <[email protected]> wrote: > David Carlier (1): > ms/eventfs: Hold eventfs_mutex and SRCU when remount walks events > > Deepanshu Kartikey (1): > ms/eventfs: Initialize ei->children and ei->list in init_ei() > > Joseph Qi (1): > ms/eventfs: fix SRCU read lock leak in eventfs_iterate() > > Shuangpeng Bai (1): > ms/eventfs: Fix use-after-free in eventfs_remove_rec() > > Steven Rostedt (1): > ms/eventfs: Use children field for rcu head and add memory barriers The backports match their mainline and 6.12.y originals, and the end state fixes the eventfs_iterate() oops. 6.12.y applies the init_ei() fix before 1b95382da85c, so with the reorder the order is the same as there and 3/5 no longer warns on the events dir failure path. Separate patches, not needed for this series; I created a task for each: 1. 6.12.y 1801ce6ce6f9 (mainline f67950b2887f, "eventfs: Use list_add_tail_rcu() for SRCU-protected children list"). eventfs_create_dir() still publishes the child with a plain list_add_tail() on the list that eventfs_iterate() walks under SRCU. It is Cc stable and from the same family as 1/5. https://virtuozzo.atlassian.net/browse/VSTOR-154848 2. Mainline 2cd88c498ecf ("eventfs: Free the eventfs_inode after an rcu grace period too"), Cc stable. tracefs_d_revalidate() reads ei->is_freed in RCU path walk, but the ei is freed after an SRCU grace period only, which does not wait for rcu_read_lock() sections. https://virtuozzo.atlassian.net/browse/VSTOR-154849 -- Konstantin Khorenko, Virtuozzo Linux Kernel Team _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
