public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 05/10] liveupdate: Defer FLB module refcounting to active sessions
Date: Thu, 02 Apr 2026 16:21:16 +0000	[thread overview]
Message-ID: <2vxza4vlfi4j.fsf@kernel.org> (raw)
In-Reply-To: <20260327033335.696621-6-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 27 Mar 2026 03:33:29 +0000")

On Fri, Mar 27 2026, Pasha Tatashin wrote:

> Stop pinning modules indefinitely upon FLB registration.
> Instead, dynamically take a module reference when the FLB is actively
> used in a session (e.g., during preserve and retrieve) and release it
> when the session concludes.
>
> This allows modules providing FLB operations to be cleanly unloaded
> when not in active use by the live update orchestrator.
>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>

This is good for now but I think we should rework the FLB registration
down the line. File handlers should not use the FLB before registering
first, and we should initialize the FLB on registration. At this point,
if there is incoming data for the FLB the module reference should be
taken since now there are files depending on that module.

Reviewed-by: Pratyush Yadav (Google) <pratyush@kernel.org>

[...]

-- 
Regards,
Pratyush Yadav

  parent reply	other threads:[~2026-04-02 16:21 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 [this message]
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
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=2vxza4vlfi4j.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