[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181217114922.km7dhpcuevjog3d3@pathway.suse.cz>
Date: Mon, 17 Dec 2018 12:49:22 +0100
From: Petr Mladek <pmladek@...e.com>
To: Joe Lawrence <joe.lawrence@...hat.com>
Cc: Nicholas Mc Guire <hofrat@...dl.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Jessica Yu <jeyu@...nel.org>, Jiri Kosina <jikos@...nel.org>,
Miroslav Benes <mbenes@...e.cz>, live-patching@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] livepatch: fix non-static warnings
On Fri 2018-12-14 16:34:23, Joe Lawrence wrote:
> Almost. We should only need to annotate with __noclone for those
> function definitions which the samples will be patching. As the commit
> message says, these correlate to klp_func.old_name functions found in
> klp_object.name objects (.ko modules or NULL for vmlinux).
>
> For the functions defined in samples/livepatch/*.c those would be:
>
> livepatch-callbacks-busymod.c :: busymod_work_func()
__noclone is not added to this function in v2. Well, I wonder
if it can be optimized when it is passed as a pointer.
> livepatch-shadow-mod.c :: dummy_alloc()
> livepatch-shadow-mod.c :: dummy_free()
> livepatch-shadow-mod.c :: dummy_check()
>
> So even though livepatch-shadow-fix2 further refines
> livepatch-shadow-fix1, the livepatch core is going to redirect the
> original dummy_*() calls defined by livepatch-shadow-mod.c in both fix1
> and fix2 cases. Ie, the fixes modules aren't patched, only the original.
Best Regards,
Petr
Powered by blists - more mailing lists