All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: bugs with ckpt-v15-dev
Date: Mon, 18 May 2009 17:39:19 -0500	[thread overview]
Message-ID: <20090518223919.GA24826@us.ibm.com> (raw)
In-Reply-To: <m3y6suhz5g.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>

Quoting Nathan Lynch (ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org):
> "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> writes:
> 
> > Quoting Nathan Lynch (ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org):
> >> Last commit is ed3b275 "allow error string during checkpoint while
> >> holding a spinlock".
> >> 
> >> # bash -c 'exec <&- >&- 2>&- ; while : ; do : ; done' &
> >> [1] 2269
> >> # ckpt $! > /tmp/bash.ckpt
> >> 
> >> BUG: sleeping function called from invalid context at mm/slub.c:1595
> >
> > Yeah, not only does ckpt_write_err() get called under task_lock, but
> > the fn returns without ver doing put_task_struct.  (I'd generate and
> > send the quick trivial patch, but my git tree is in a bit of a debugme
> > state right now)
> 
> Would prefer to just rip that thing out, it's cost me more trouble then
> it's worth.

Which thing - CHECKPOINT_SUBTREE, freezer check, or ckpt_write_err?

> > Now mind you this shows that your ckpt program isn't sending
> > CHECKPOINT_SUBTREE with flags.
> 
> I don't follow.  There is "user error" here in that I'm not freezing the
> task before checkpointing[1], but my ckpt command is passing the subtree
> flag (0x4) afaict:
> 
> SYS_335(0x9ec, 0x1, 0x4, 0xbfdc6200, 0[2542:c/r:may_checkpoint_task] check 2540

Oh, it's the freezer test in may_checkpoint_task you're getting the
error on?  (in my git tree I'd commented that one out temporarily so I
just assumed it was the subtree check in get_container :)

> > This in turns means you are probably
> > not using the ckpt-v15-dev version of user-cr, and if that is
> > the case it makes your problems with gconf shared file mapping more
> > suspect ask well...?
> 
> After updating to the latest user-cr I get the same BUGs.
> 
> [1] Should CONFIG_CHECKPOINT depend on CONFIG_CGROUPS and/or
> CONFIG_CGROUPS_FREEZER?  We require tasks to be put in frozen state
> before checkpoint, is there any mechanism apart from
> cgroup/freezer.state to do this?

A task can self-checkpoint without the freezer though.

-serge

  parent reply	other threads:[~2009-05-18 22:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 19:23 bugs with ckpt-v15-dev Nathan Lynch
     [not found] ` <m3my9amczw.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-05-18 21:10   ` Serge E. Hallyn
     [not found]     ` <20090518211041.GA20781-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-18 21:36       ` Nathan Lynch
     [not found]         ` <m3y6suhz5g.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-05-18 22:39           ` Serge E. Hallyn [this message]
     [not found]             ` <20090518223919.GA24826-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-18 23:02               ` Nathan Lynch
2009-05-18 22:51           ` Matt Helsley
     [not found]             ` <20090518225100.GC28083-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-18 23:21               ` Nathan Lynch
     [not found]                 ` <m3zldagfpp.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-05-19  1:09                   ` Matt Helsley
     [not found]                     ` <20090519010911.GD28083-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-20  5:30                       ` Oren Laadan
     [not found]                         ` <4A13955E.2040301-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-05-20 13:14                           ` Serge E. Hallyn
     [not found]                             ` <20090520131457.GB25989-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-20 13:21                               ` Oren Laadan
2009-05-20 21:10                               ` Matt Helsley
2009-05-20  5:28   ` 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=20090518223919.GA24826@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.