public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Matlack <dmatlack@google.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@kernel.org>,
	 Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	 Samiullah Khawaja <skhawaja@google.com>,
	David Matlack <dmatlack@google.com>
Subject: [PATCH 0/2] liveupdate: FLB refcounting improvements
Date: Thu, 23 Apr 2026 17:40:27 +0000	[thread overview]
Message-ID: <20260423174032.3140399-1-dmatlack@google.com> (raw)

This series can be found on GitHub:

  https://github.com/dmatlack/linux/tree/liveupdate/flb/refcount/v1

This series has 2 patches to improve how FLB refcounting works in
preparation for using FLB in the PCI core. The first patch converts the
existing refcounting to use refcount_t, and the second patch allows
users of the incoming FLB to hold references to the FLB to avoid it
getting freed.

Users of the outgoing FLB don't need to take an extra reference yet
since it's always done in the context of a preserve/unpreserve file
callback, which are already synchronized with outgoing FLB creation
and destruction.

This series has been tested against the existing Live Update selftests
(liveupdate, luo_kexec_simple, and luo_multi_session) on an Intel EMR
host.


David Matlack (2):
  liveupdate: Use refcount_t for FLB reference counts
  liveupdate: Reference count incoming FLB data

 include/linux/liveupdate.h  |  9 ++++++-
 kernel/liveupdate/luo_flb.c | 52 ++++++++++++++++++-------------------
 lib/tests/liveupdate.c      |  3 +++
 3 files changed, 37 insertions(+), 27 deletions(-)


base-commit: 2a4c0c11c0193889446cdb6f1540cc2b9aff97dd
-- 
2.54.0.rc2.544.gc7ae2d5bb8-goog


             reply	other threads:[~2026-04-23 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 17:40 David Matlack [this message]
2026-04-23 17:40 ` [PATCH 1/2] liveupdate: Use refcount_t for FLB reference counts David Matlack
2026-04-23 18:11   ` Pasha Tatashin
2026-04-23 18:49     ` David Matlack
2026-04-23 19:40       ` Pasha Tatashin
2026-04-23 19:58   ` Samiullah Khawaja
2026-04-23 17:40 ` [PATCH 2/2] liveupdate: Reference count incoming FLB data David Matlack
2026-04-23 18:21   ` Pasha Tatashin
2026-04-23 19:46   ` Samiullah Khawaja
2026-04-23 18:13 ` [PATCH 0/2] liveupdate: FLB refcounting improvements Pasha Tatashin
2026-04-23 18:40   ` David Matlack

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=20260423174032.3140399-1-dmatlack@google.com \
    --to=dmatlack@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --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