From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Jessica Yu <jeyu@redhat.com>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v3] livepatch: introduce shadow variable API
Date: Fri, 11 Aug 2017 11:35:11 -0500 [thread overview]
Message-ID: <20170811163511.psyran7h2zvsxtfk@treble> (raw)
In-Reply-To: <1501262722-26502-2-git-send-email-joe.lawrence@redhat.com>
On Fri, Jul 28, 2017 at 01:25:22PM -0400, Joe Lawrence wrote:
> Add exported API for livepatch modules:
>
> klp_shadow_get()
> klp_shadow_attach()
> klp_shadow_get_or_attach()
> klp_shadow_update_or_attach()
> klp_shadow_detach()
> klp_shadow_detach_all()
I like the API.
> +Matching parent's lifecycle
> +---------------------------
> +
> +If parent data structures are frequently created and destroyed, it may
> +be easiest to align its shadow variable lifetimes to the same allocation
"its shadow variable lifetimes" -> "their shadow variables' lifetimes" ?
> +void *klp_shadow_attach(void *obj, unsigned long id, void *data,
> + size_t size, gfp_t gfp_flags)
[ Note: some of the following comments also apply to
klp_shadow_get_or_attach and klp_shadow_update_or_attach. ]
> +{
> + struct klp_shadow *new_shadow;
nit: The "new" is implied, and there's only one shadow struct used in
the function, so maybe just call it "shadow"?
> + void *shadow_data;
> + unsigned long flags;
> +
> + /* Take error exit path if <obj, id> already exists */
> + shadow_data = klp_shadow_get(obj, id);
> + if (unlikely(shadow_data))
> + goto err_exists;
The return value of klp_shadow_get() can be tested directly, no need for
a variable.
> + /* Allocate a new shadow variable for use inside the lock below */
> + new_shadow = kzalloc(size + sizeof(*new_shadow), gfp_flags);
> + if (!new_shadow)
> + goto err;
The goto destination is just a single line return, so I think it's
clearer to just return NULL here and get rid of the err label.
> +
> + /* Look for <obj, id> again under the lock */
> + spin_lock_irqsave(&klp_shadow_lock, flags);
> + shadow_data = klp_shadow_get(obj, id);
> + if (unlikely(shadow_data)) {
> +
> + /* Shadow variable found, throw away allocation and take
> + * error exit path */
Multi-line comments should be in the kernel coding style:
/*
* Shadow variable found, throw away allocation and take
* error exit path
*/
Also, complete sentences preferred :-)
> + spin_unlock_irqrestore(&klp_shadow_lock, flags);
> + kfree(shadow_data);
Shouldn't it free new_shadow instead of shadow_data?
> + goto err_exists;
> + }
> +
> + /* No <obj, id> found, add the newly allocated one */
> + shadow_data = data;
> + klp_shadow_set(new_shadow, obj, id, data, size);
To avoid doing extra work with the lock held, the klp_shadow_set() can
be done before getting the lock, after the kzalloc.
--
Josh
next prev parent reply other threads:[~2017-08-11 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 17:25 [PATCH v3] livepatch: shadow variables Joe Lawrence
2017-07-28 17:25 ` [PATCH v3] livepatch: introduce shadow variable API Joe Lawrence
2017-08-10 14:40 ` Miroslav Benes
2017-08-10 16:04 ` Joe Lawrence
2017-08-11 6:27 ` Miroslav Benes
2017-08-11 16:35 ` Josh Poimboeuf [this message]
2017-08-14 13:56 ` Joe Lawrence
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=20170811163511.psyran7h2zvsxtfk@treble \
--to=jpoimboe@redhat.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.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
all inboxes | Powered by JetHome®