All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/5] ms/eventfs: fix kernel panic on NULL dereference
Date: Thu, 12 Nov 2026 17:43:06 +0100	[thread overview]
Message-ID: <179450178653.4060562.533631543654557900.b4-review@b4> (raw)
In-Reply-To: <20261112000926.381308-2-eva.kurchatova@virtuozzo.com>

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 <eva.kurchatova@virtuozzo.com> 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
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  parent reply	other threads:[~2026-11-12 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  0:07 Eva Kurchatova
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 1/5] ms/eventfs: Hold eventfs_mutex and SRCU when remount walks events Eva Kurchatova
2026-11-12  0:15   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 2/5] ms/eventfs: Fix use-after-free in eventfs_remove_rec() Eva Kurchatova
2026-11-12  0:13   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 3/5] ms/eventfs: Use children field for rcu head and add memory barriers Eva Kurchatova
2026-11-12  0:16   ` no-reply
2026-11-12  4:18     ` Eva Kurchatova (Virtuozzo)
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 4/5] ms/eventfs: fix SRCU read lock leak in eventfs_iterate() Eva Kurchatova
2026-11-12  0:15   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 5/5] ms/eventfs: Initialize ei->children and ei->list in init_ei() Eva Kurchatova
2026-11-12  0:16   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12 16:43 ` Konstantin Khorenko [this message]
2026-11-12 16:50 ` [Devel] [PATCH hci-8.1 v2 0/5] ms/eventfs: fix kernel panic on NULL dereference Konstantin Khorenko

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=179450178653.4060562.533631543654557900.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=eva.kurchatova@virtuozzo.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.