All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Sharyathi Nagesh <sharyath@in.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Paul Menage <menage@google.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	balbir <balbir@linux.vnet.ibm.com>,
	"Rishikesh K. Rajak" <risrajak@in.ibm.com>,
	akpm@linux-foundation.org
Subject: Re: Error with cgroups: "unused subsystem ns"
Date: Wed, 17 Dec 2008 19:08:41 -0600	[thread overview]
Message-ID: <20081218010841.GA17385@hallyn.com> (raw)
In-Reply-To: <4948D3C4.9060900@in.ibm.com>

Quoting Sharyathi Nagesh (sharyath@in.ibm.com):
> Hi
>
> Description:
>   We have noticed kernel error message on the dmesg when ltp test cases are 
> executed. We observed multiple instance of error message:
>                   "Not cloning cgroup for unused subsystem ns" in dmesg
>
> Test:
> The messages were seen when ltp test case for the containers are executed:
> ltp -f containers
>
> Solution:
> Alexey Dobriyan had provided a patch to address the issue. Where the printk 
> was removed. The patch still haven't made it to main line and hence we 
> still see the messages.
> The patch can be found here:
>  http://git.openvz.org/?p=linux-2.6.24-openvz;a=log;h=v2.6.24-ovz002.2
>
> Would this be the right way to handle the issue?
> if so
> When can we expect this to be included into mainline

Resend the patch to lkml.  Assuming you are talking about commit id
93af30a60055a83a00188ae04b88bbd9b4e1489a, go ahead and add my
Acked-by.

Converting it to a pr_debug() might be another thing to consider, but
I'm not sure anyone wants these messages.

-serge

  reply	other threads:[~2008-12-18  1:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 10:26 Error with cgroups: "unused subsystem ns" Sharyathi Nagesh
2008-12-18  1:08 ` Serge E. Hallyn [this message]
2008-12-18 11:15   ` Sharyathi Nagesh
2008-12-18 19:12     ` Andrew Morton
2008-12-19 17:17       ` Sharyathi Nagesh

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=20081218010841.GA17385@hallyn.com \
    --to=serge@hallyn.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=risrajak@in.ibm.com \
    --cc=sharyath@in.ibm.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 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.