From: Liu Kui <kui.liu@virtuozzo.com>
To: Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: azaitsev@virtuozzo.com, devel@openvz.org,
Liu Kui <kui.liu@virtuozzo.com>
Subject: [Devel] [PATCH hci-8.0 0/2] fs/fuse: unify dropping the fuse file reference of a writeback request
Date: Wed, 23 Sep 2026 20:50:39 +0800 [thread overview]
Message-ID: <20260923-vstor-145614-unify-v1-0-3907084ba107@virtuozzo.com> (raw)
Rework the fix for the fuse file refcount leak on close_wait writeback
(VSTOR-145614): revert the previous fix, which moved the wpa's
reference acquisition back to submit time, and instead drop the
reference unconditionally in fuse_writepage_free(), which every wpa
death path passes exactly once. This keeps the allocation-time
ownership model of mainline commit 4046d3adcca4 ("fuse: move fuse file
initialization to wpa allocation time") unmodified.
https://virtuozzo.atlassian.net/browse/VSTOR-145614
---
Liu Kui (2):
Revert "fs/fuse: fix fuse file refcount leak on close_wait writeback"
fs/fuse: unify dropping the fuse file reference of a writeback request
fs/fuse/file.c | 14 +++-----------
1 file changed, 3 insertions(+), 11 deletions(-)
---
base-commit: f2a619dddfc50f37d3255d68a33b78bbae2d65ad
change-id: 20260923-vstor-145614-unify-d7c8392ff890
Best regards,
--
Liu Kui <kui.liu@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-09-23 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 12:50 Liu Kui [this message]
2026-09-23 12:50 ` [Devel] [PATCH hci-8.0 1/2] Revert "fs/fuse: fix fuse file refcount leak on close_wait writeback" Liu Kui
2026-09-23 12:50 ` [Devel] [PATCH hci-8.0 2/2] fs/fuse: unify dropping the fuse file reference of a writeback request Liu Kui
2026-09-23 17:26 ` Konstantin Khorenko
2026-09-23 17:01 ` [Devel] [PATCH hci-8.0 0/2] " Konstantin Khorenko
2026-09-23 17:13 ` 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=20260923-vstor-145614-unify-v1-0-3907084ba107@virtuozzo.com \
--to=kui.liu@virtuozzo.com \
--cc=azaitsev@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@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.