Linux Container Development
 help / color / mirror / Atom feed
From: Subrata Modak <subrata-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
	Veerendra
	<veeren-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: ltp-list
	<ltp-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	Veerendra Chandrappa
	<vechandr-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>,
	Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Serge Hallyn
	<serue-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [TESTING] Device whitelist on cgroups
Date: Sun, 31 Aug 2008 00:15:57 +0530	[thread overview]
Message-ID: <1220121957.5034.9.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20080826160003.GA21827-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


On Tue, 2008-08-26 at 11:00 -0500, Serge E. Hallyn wrote:
> Quoting Pavel Emelyanov (xemul@openvz.org):
> > Serge E. Hallyn wrote:
> > > Quoting Subrata Modak (subrata@linux.vnet.ibm.com):
> > >> Serge,
> > >>
> > >> I have another doubt. Are we also having the plan(s) to add testcases
> > >> for testing this new feature (Device whitelist on cgroups) added in
> > >> 2.6.26 under the DEVICE NAMESPACE category !!
> > >>
> > >> Regards--
> > >> Subrata
> > > 
> > > That's something I expect Veerendra would do next year.  (Veerendra,
> > > if you have time this year, please let me know).
> > > 
> > > It also seems likely that the openvz folks, who are using this,
> > > have some testcases they could share.  Pavel?
> > 
> > We have and we could share them, but unfortunately their 
> > *implementation* is completely useless without the whole 
> > testing infrastructure we use (which it turn is too heavy
> > and too Virtuozzo-specific to be shared).
> > 
> > All I can is provide a single testcase we perform: set some
> > permissions and check that the allowed devices are allowed
> > and not allowed are not allowed ;)
> 
> Ok, thanks, Pavel.  Sounds like starting from scratch would be
> the simplest thing here.

Pavel,

You can even share that single test case with us. This can help
Veerendra to get a direction when he starts writing for DEVICE Namespace
test cases either this year, or, next year. I feel it´s always better to
get a good start if we have some direction in our hands. Pavel, please
share the same.

Regards--
Subrata

> 
> -serge

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

      parent reply	other threads:[~2008-08-30 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1219699261.5434.22.camel@subratamodak.linux.ibm.com>
     [not found] ` <1219699261.5434.22.camel-NRFfyExJdYpgXGGE5LP+UZlqa2bBAFbm0E9HWUfgJXw@public.gmane.org>
2008-08-26 13:33   ` [TESTING] Device whitelist on cgroups Serge E. Hallyn
     [not found]     ` <20080826133358.GB12266-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-08-26 14:14       ` Pavel Emelyanov
     [not found]         ` <48B40FC7.2000900-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-08-26 16:00           ` Serge E. Hallyn
     [not found]             ` <20080826160003.GA21827-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-08-30 18:45               ` Subrata Modak [this message]

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=1220121957.5034.9.camel@subratamodak.linux.ibm.com \
    --to=subrata-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=ltp-list-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=serue-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=vechandr-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
    --cc=veeren-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=xemul-GEFAQzZX7r8dnm+yROfE0A@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