From: Mike Rapoport <rppt@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Pratyush Yadav <pratyush@kernel.org>
Subject: Re: [PATCH 0/2] liveupdate: luo_session: Fix a couple Smatch issues
Date: Thu, 27 Nov 2025 07:10:42 +0200 [thread overview]
Message-ID: <aSfdUksD7kOkVFjn@kernel.org> (raw)
In-Reply-To: <aSfcq505vVuGo80M@kernel.org>
Wrong thread, sorry for the noise
On Thu, Nov 27, 2025 at 07:07:55AM +0200, Mike Rapoport wrote:
> (added Dan Carpenter)
>
> On Wed, Nov 26, 2025 at 05:51:23PM +0300, Dan Carpenter wrote:
> > Smatch detected these two bugs.
> >
> > Dan Carpenter (2):
> > liveupdate: luo_session: Fix uninitialized variable in
> > luo_session_setup_outgoing()
> > liveupdate: luo_session: Fix use after free in
> > luo_session_deserialize()
> >
> > kernel/liveupdate/luo_session.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > --
> > 2.51.0
> >
>
> --
> Sincerely yours,
> Mike.
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2025-11-27 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 14:51 [PATCH 0/2] liveupdate: luo_session: Fix a couple Smatch issues Dan Carpenter
2025-11-26 14:51 ` [PATCH 1/2] liveupdate: luo_session: Fix uninitialized variable in luo_session_setup_outgoing() Dan Carpenter
2025-11-26 15:22 ` Pasha Tatashin
2025-11-26 14:51 ` [PATCH 2/2] liveupdate: luo_session: Fix use after free in luo_session_deserialize() Dan Carpenter
2025-11-26 15:23 ` Pasha Tatashin
2025-11-26 15:25 ` [PATCH 0/2] liveupdate: luo_session: Fix a couple Smatch issues Pasha Tatashin
2025-11-27 5:07 ` Mike Rapoport
2025-11-27 5:10 ` Mike Rapoport [this message]
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=aSfdUksD7kOkVFjn@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@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