From: Nicolai Stange <nstange@suse.de>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: raschupkin.ri@gmail.com, live-patching@vger.kernel.org,
pmladek@suse.com, mbenes@suse.cz, jikos@kernel.org,
jpoimboe@kernel.org
Subject: Re:
Date: Tue, 16 Jul 2024 11:28:57 +0200 [thread overview]
Message-ID: <877cdlsn1i.fsf@> (raw)
In-Reply-To: <ZpWEifTpQ1vc1naA@redhat.com> (Joe Lawrence's message of "Mon, 15 Jul 2024 16:20:25 -0400")
Hi all,
Joe Lawrence <joe.lawrence@redhat.com> writes:
> On Sun, Jul 14, 2024 at 09:59:32PM +0200, raschupkin.ri@gmail.com wrote:
>>
> But first, let me see if I understand the problem correctly. Let's say
> points A and A' below represent the original kernel code reference
> get/put pairing in task execution flow. A livepatch adds a new get/put
> pair, B and B' in the middle like so:
>
> --- execution flow --->
> -- A B B' A' -->
>
> There are potential issues if the livepatch is (de)activated
> mid-sequence, between the new pairings:
>
> problem 1:
> -- A . B' A' --> 'B, but no B = extra put!
> ^ livepatch is activated here
>
> problem 2:
> -- A B . A' --> B, but no B' = extra get!
> ^ livepatch is deactivated here
I can confirm that this scenario happens quite often with real world CVE
fixes and there's currently no way to implement such changes safely from
a livepatch. But I also believe this is an instance of a broader problem
class we attempted to solve with that "enhanced" states API proposed and
discussed at LPC ([1], there's a link to a recording at the bottom). For
reference, see Petr's POC from [2].
> The first thing that comes to mind is that this might be solved using
> the existing shadow variable API.
Same.
> When the livepatch takes the new
> reference (B), it could create a new <struct, NEW_REF> shadow variable
> instance. The livepatch code to return the reference (B') would then
> check on the shadow variable existence before doing so. This would
> solve problem 1.
>
> The second problem is a little trickier. Perhaps the shadow variable
> approach still works as long as a pre-unpatch hook* were to iterate
> through all the <*, NEW_REF> shadow variable instances and returned
> their reference before freeing the shadow variable and declaring the
> livepatch inactive.
I think the problem of consistently maintaining shadowed reference
counts (or anything shadowed for that matter) could be solved with the
help of aforementioned states API enhancements, so I would propose to
revive Petr's IMO more generic patchset as an alternative.
Thoughts?
Thanks,
Nicolai
[1] https://lpc.events/event/17/contributions/1541/
[2] https://lore.kernel.org/r/20231110170428.6664-1-pmladek@suse.com
--
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany
GF: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2024-07-16 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 19:59 raschupkin.ri
2024-07-14 19:59 ` [PATCH 1/2] [PATCH] livepatch: support of modifying refcount_t without underflow after unpatch raschupkin.ri
2024-07-14 22:07 ` Jeff Johnson
2024-07-14 19:59 ` [PATCH 2/2] selftests/livepatch: Add tests for kprefcount_t support raschupkin.ri
2024-07-15 20:20 ` Joe Lawrence
2024-07-15 22:45 ` Re: Roman Rashchupkin
2024-07-16 9:28 ` Nicolai Stange [this message]
[not found] ` <66963d60.170a0220.70a9a.8866SMTPIN_ADDED_BROKEN@mx.google.com>
2024-07-16 9:53 ` Re: Roman Rashchupkin
2024-07-25 14:52 ` Re: Joe Lawrence
2024-07-16 17:33 ` Re: Song Liu
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=877cdlsn1i.fsf@ \
--to=nstange@suse.de \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=raschupkin.ri@gmail.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