Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH 2/2] [RFC] Add checkpoint/restart support for epoll files.
Date: Tue, 25 Aug 2009 00:17:08 -0400	[thread overview]
Message-ID: <4A9365C4.3010305@librato.com> (raw)
In-Reply-To: <20090825020146.GC8078-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>



Matt Helsley wrote:
> On Mon, Aug 24, 2009 at 04:27:25PM -0500, Serge E. Hallyn wrote:
>> Quoting Matt Helsley (matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org):
>>> Save/restore epoll items during checkpoint/restart respectively.

[...]

>>> +/* TODO confirm that get_current_user() has been restored */
>> Not sure what you mean.  At this point, the task's credentials
>> are still the ones used when it called sys_restart().  We won't
>> update them until the end of the restart operation.  However the
>> normal file restore operations should have reset the file->f_cred
>> to the checkpointed value - including hierarchical user namespaces.
> 
> I wanted to check to ensure that we're properly enforcing the epoll
> watch limits for the restarted tasks. So the patch looks good because
> it restore the "common" file pieces before the epoll items/watches.
> See below if you're curious where/how that happens. I think I can
> remove this TODO now.

Good point. Me thinks it deserves a comment in the code ?

Oren.

  parent reply	other threads:[~2009-08-25  4:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  5:17 [PATCH 1/2] Check for valid destructor pointer before calling it Matt Helsley
     [not found] ` <6d896e12f316e5ff5f44bd13ae1482dab7f9253a.1250745409.git.matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-08-20  5:17   ` [PATCH 2/2] [RFC] Add checkpoint/restart support for epoll files Matt Helsley
     [not found]     ` <e820d207a3b1a3228ded29bce9b29f2179ab598b.1250745409.git.matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-08-20 16:33       ` Oren Laadan
     [not found]         ` <4A8D7AE2.1030705-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-08-25  5:17           ` Matt Helsley
     [not found]             ` <20090825051723.GD8078-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2009-08-25 17:42               ` Oren Laadan
     [not found]                 ` <4A94227C.9050101-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-08-26  9:00                   ` Matt Helsley
2009-08-24 21:27       ` Serge E. Hallyn
     [not found]         ` <20090824212725.GA25030-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-08-25  2:01           ` Matt Helsley
     [not found]             ` <20090825020146.GC8078-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2009-08-25  4:17               ` Oren Laadan [this message]
     [not found]                 ` <4A9365C4.3010305-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-08-25 12:09                   ` Matt Helsley
2009-08-20 12:28   ` [PATCH 1/2] Check for valid destructor pointer before calling it Oren Laadan

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=4A9365C4.3010305@librato.com \
    --to=orenl-rdfvbdnroixbdgjk7y7tuq@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@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