From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: Supporting patches for netns/netdev (v2)
Date: Tue, 09 Feb 2010 14:10:18 -0800 [thread overview]
Message-ID: <87y6j2giwl.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: <4B71DC2B.1070107-eQaUEPhvms7ENvBUuze7eA@public.gmane.org> (Oren Laadan's message of "Tue\, 09 Feb 2010 17\:05\:31 -0500")
OL> Both look good.
Okay, but per Serge's suggestion shall we change the restore_obj() to
the one included below? :)
--
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
commit d0c71c159decd47c4a6f9778d02dc521b74ff414
Author: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Date: Tue Feb 9 14:04:23 2010 -0800
Make restore_obj() tolerate a preexisting object in the hash (v2)
... as long as the pointer is the same as that returned from the restore
function. Also move the compulsory ref_drop() so that it only gets
done if we created the new object.
The existing object tolerance is important for netdev restore because it
means that I can refer to a peer by its objref instead of needing the
(previously-rejected) veth_peer() function. If this is not acceptable,
then I'll need to keep a separate list of pairs.
Changes in v2:
- Check that the type of the object already in the hash matches that
of the objref header we're reading.
- Add a comment about why and how we might get into this sort of
situation.
Signed-off-by: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
diff --git a/checkpoint/objhash.c b/checkpoint/objhash.c
index 0b06b06..4ca7799 100644
--- a/checkpoint/objhash.c
+++ b/checkpoint/objhash.c
@@ -1059,16 +1059,29 @@ int restore_obj(struct ckpt_ctx *ctx, struct ckpt_hdr_ob
if (IS_ERR(ptr))
return PTR_ERR(ptr);
- if (obj_find_by_objref(ctx, h->objref))
- obj = ERR_PTR(-EINVAL);
- else
+ obj = obj_find_by_objref(ctx, h->objref);
+ if (!obj) {
obj = obj_new(ctx, ptr, h->objref, h->objtype);
- /*
- * Drop an extra reference to the object returned by ops->restore:
- * On success, this clears the extra reference taken by obj_new(),
- * and on failure, this cleans up the object itself.
- */
- ops->ref_drop(ptr, 0);
+ /*
+ * Drop an extra reference to the object returned by
+ * ops->restore: On success, this clears the extra
+ * reference taken by obj_new(), and on failure, this
+ * cleans up the object itself.
+ */
+ ops->ref_drop(ptr, 0);
+ } else if ((obj->ptr != ptr) || (obj->ops->obj_type != h->objtype)) {
+ /* Normally, we expect an object to not already exist
+ * in the hash. However, for some special scenarios
+ * where we're restoring sets of objects that must be
+ * co-allocated (such, as veth netdev pairs) we need
+ * to tolerate this case if the second restore returns
+ * the correct type and pointer, as specified in the
+ * existing object. If either of those don't match,
+ * we fail.
+ */
+ obj = ERR_PTR(-EINVAL);
+ }
+
if (IS_ERR(obj)) {
ops->ref_drop(ptr, 1);
return PTR_ERR(obj);
next prev parent reply other threads:[~2010-02-09 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 21:11 Supporting patches for netns/netdev (v2) Dan Smith
[not found] ` <1265749870-13989-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-09 21:11 ` [PATCH 1/2] Make restore_obj() tolerate a preexisting object in the hash (v2) Dan Smith
2010-02-09 21:11 ` [PATCH 2/2] Move ckpt_objhash_free() to before we destroy the deferqueues Dan Smith
2010-02-09 22:05 ` Supporting patches for netns/netdev (v2) Oren Laadan
[not found] ` <4B71DC2B.1070107-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-09 22:10 ` Dan Smith [this message]
[not found] ` <87y6j2giwl.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-02-09 22:11 ` Oren Laadan
2010-02-09 22:32 ` Serge E. Hallyn
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=87y6j2giwl.fsf@caffeine.danplanet.com \
--to=danms-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.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