mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leo Timmins <leotimmins1974@gmail.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
	Mike Rapoport <rppt@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Leo Timmins <leotimmins1974@gmail.com>
Subject: [PATCH v2 0/2] liveupdate: fix incoming error handling and teardown paths
Date: Wed, 25 Mar 2026 12:46:06 +0800	[thread overview]
Message-ID: <20260325044608.8407-1-leotimmins1974@gmail.com> (raw)

Hi,

This series fixes two issues in LUO's incoming-side error handling and
teardown paths.

The first patch makes session deserialization fail when file
deserialization fails, instead of silently continuing with a partially
restored session.

The second patch (formerly patch 3 on the v1) initializes incoming FLB
state before the finish pathdecrements its refcount, so the last-user
cleanup path does not run from an uninitialized count. (and now 
utilises pr_warn instead of WARN_ON)

Changes in v2:

  - drop the previous patch 2 after review
  - patch 2/2: replace WARN_ON(err) with pr_warn() in
    luo_flb_file_finish_one()

Leo Timmins (2):
  liveupdate: propagate file deserialization failures
  liveupdate: initialize incoming FLB state before finish

 kernel/liveupdate/luo_flb.c     | 19 ++++++++++++++++++-
 kernel/liveupdate/luo_session.c |  9 +++++++--
 2 files changed, 25 insertions(+), 3 deletions(-)


base-commit: e3c33bc767b5512dbfec643a02abf58ce608f3b2
-- 
2.53.0

             reply	other threads:[~2026-03-25  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25  4:46 Leo Timmins [this message]
2026-03-25  4:46 ` [PATCH v2 1/2] liveupdate: propagate file deserialization failures Leo Timmins
2026-03-25 13:05   ` Pasha Tatashin
2026-03-26  3:50   ` Andrew Morton
2026-03-25  4:46 ` [PATCH v2 2/2] liveupdate: initialize incoming FLB state before finish Leo Timmins
2026-03-25 13:08   ` Pasha Tatashin

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=20260325044608.8407-1-leotimmins1974@gmail.com \
    --to=leotimmins1974@gmail.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 \
    /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

all inboxes | Powered by JetHome®