From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: rppt@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, dmatlack@google.com,
pratyush@kernel.org, skhawaja@google.com
Subject: Re: [PATCH v3 07/10] liveupdate: Auto unregister FLBs on file handler unregistration
Date: Fri, 03 Apr 2026 10:17:14 +0000 [thread overview]
Message-ID: <2vxzika8e4b9.fsf@kernel.org> (raw)
In-Reply-To: <20260327033335.696621-8-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 27 Mar 2026 03:33:31 +0000")
On Fri, Mar 27 2026, Pasha Tatashin wrote:
> To ensure that unregistration is always successful and doesn't leave
> dangling resources, introduce auto-unregistration of FLBs: when a file
> handler is unregistered, all FLBs associated with it are automatically
> unregistered.
>
> Introduce a new helper luo_flb_unregister_all() which unregisters all
> FLBs linked to the given file handler.
>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> ---
> kernel/liveupdate/luo_file.c | 14 +-----
> kernel/liveupdate/luo_flb.c | 84 ++++++++++++++++++++++----------
> kernel/liveupdate/luo_internal.h | 1 +
> 3 files changed, 60 insertions(+), 39 deletions(-)
>
> diff --git a/kernel/liveupdate/luo_file.c b/kernel/liveupdate/luo_file.c
> index 439177c10723..80f4e3b796a6 100644
> --- a/kernel/liveupdate/luo_file.c
> +++ b/kernel/liveupdate/luo_file.c
> @@ -895,26 +895,16 @@ int liveupdate_register_file_handler(struct liveupdate_file_handler *fh)
> */
> int liveupdate_unregister_file_handler(struct liveupdate_file_handler *fh)
> {
> - int err = -EBUSY;
> -
> if (!liveupdate_enabled())
> return -EOPNOTSUPP;
>
> liveupdate_test_unregister(fh);
>
> - down_write(&luo_register_rwlock);
> - if (!list_empty(&ACCESS_PRIVATE(fh, flb_list)))
> - goto err_unlock;
> -
> + guard(rwsem_write)(&luo_register_rwlock);
> + luo_flb_unregister_all(fh);
> list_del(&ACCESS_PRIVATE(fh, list));
> - up_write(&luo_register_rwlock);
>
> module_put(fh->ops->owner);
>
> return 0;
> -
> -err_unlock:
> - up_write(&luo_register_rwlock);
> - liveupdate_test_register(fh);
> - return err;
> }
> diff --git a/kernel/liveupdate/luo_flb.c b/kernel/liveupdate/luo_flb.c
> index ac6fa5b34b43..f8348138de70 100644
> --- a/kernel/liveupdate/luo_flb.c
> +++ b/kernel/liveupdate/luo_flb.c
> @@ -335,6 +335,62 @@ void luo_flb_file_finish(struct liveupdate_file_handler *fh)
> luo_flb_file_finish_one(iter->flb);
> }
>
> +static void luo_flb_unregister_one(struct liveupdate_file_handler *fh,
> + struct liveupdate_flb *flb)
> +{
> + struct luo_flb_private *private = luo_flb_get_private(flb);
> + struct list_head *flb_list = &ACCESS_PRIVATE(fh, flb_list);
> + struct luo_flb_link *iter;
> + bool found = false;
> +
> + /* Find and remove the link from the file handler's list */
Nit: it would be nice to have a lockdep_assert_held_write() here to
clearly show that the luo_register_rwlock must be held when modifying
the list. I know that luo_flb_unregister_all() already has one, but in
case we refactor later or add another caller.
Other than this,
Reviewed-by: Pratyush Yadav (Google) <pratyush@kernel.org>
> + list_for_each_entry(iter, flb_list, list) {
> + if (iter->flb == flb) {
> + list_del(&iter->list);
> + kfree(iter);
> + found = true;
> + break;
> + }
> + }
> +
[...]
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-04-03 10:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 3:33 [PATCH v3 00/10] liveupdate: Fix module unloading and unregister API Pasha Tatashin
2026-03-27 3:33 ` [PATCH v3 01/10] liveupdate: Safely print untrusted strings Pasha Tatashin
2026-03-27 13:16 ` Pasha Tatashin
2026-03-31 9:40 ` Pratyush Yadav
2026-03-31 9:50 ` Pratyush Yadav
2026-03-31 16:35 ` Pasha Tatashin
2026-03-27 3:33 ` [PATCH v3 02/10] liveupdate: Synchronize lazy initialization of FLB private state Pasha Tatashin
2026-03-31 10:38 ` Pratyush Yadav
2026-03-31 16:41 ` Pasha Tatashin
2026-03-31 19:22 ` Pratyush Yadav
2026-03-31 19:38 ` Pasha Tatashin
2026-03-27 3:33 ` [PATCH v3 03/10] liveupdate: Protect file handler list with rwsem Pasha Tatashin
2026-03-30 16:48 ` Samiullah Khawaja
2026-03-30 19:32 ` Pasha Tatashin
2026-03-31 19:24 ` Pratyush Yadav
2026-03-27 3:33 ` [PATCH v3 04/10] liveupdate: Protect FLB lists with luo_register_rwlock Pasha Tatashin
2026-03-31 19:33 ` Pratyush Yadav
2026-03-27 3:33 ` [PATCH v3 05/10] liveupdate: Defer FLB module refcounting to active sessions Pasha Tatashin
2026-03-30 16:56 ` Samiullah Khawaja
2026-03-30 19:28 ` Pasha Tatashin
2026-04-02 16:21 ` Pratyush Yadav
2026-03-27 3:33 ` [PATCH v3 06/10] liveupdate: Remove luo_session_quiesce() Pasha Tatashin
2026-04-02 16:27 ` Pratyush Yadav
2026-03-27 3:33 ` [PATCH v3 07/10] liveupdate: Auto unregister FLBs on file handler unregistration Pasha Tatashin
2026-04-03 10:17 ` Pratyush Yadav [this message]
2026-03-27 3:33 ` [PATCH v3 08/10] liveupdate: Remove liveupdate_test_unregister() Pasha Tatashin
2026-04-03 10:20 ` Pratyush Yadav
2026-03-27 3:33 ` [PATCH v3 09/10] liveupdate: Make unregister functions return void Pasha Tatashin
2026-03-27 14:41 ` Pasha Tatashin
2026-04-03 10:41 ` Pratyush Yadav
2026-03-27 3:33 ` [PATCH v3 10/10] liveupdate: Defer file handler module refcounting to active sessions Pasha Tatashin
2026-03-27 17:14 ` Andrew Morton
2026-04-03 10:42 ` Pratyush Yadav
2026-03-27 17:24 ` [PATCH v3 00/10] liveupdate: Fix module unloading and unregister API Andrew Morton
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=2vxzika8e4b9.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmatlack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=skhawaja@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox