linux-kernel - Re: [ckrm-tech] [patch 0/5]-Containers: Introduction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Sep 2006 09:06:10 -0700
From:	Rohit Seth <rohitseth@...gle.com>
To:	balbir@...ibm.com
Cc:	Andrew Morton <akpm@...l.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, devel@...nvz.org,
	CKRM-Tech <ckrm-tech@...ts.sourceforge.net>
Subject: Re: [ckrm-tech] [patch 0/5]-Containers: Introduction

On Mon, 2006-09-18 at 18:57 +0530, Balbir Singh wrote:
> Rohit Seth wrote:
> 
> > Below is a one line description for patches that will follow:
> > 
> > [patch01]: Documentation on how to use containers
> > (Documentation/container.txt)
> > 
> > [patch02]: Changes in the generic part of kernel code
> > 
> > [patch03]: Container's interface with configfs
> > 
> > [patch04]: Core container support
> > 
> > [patch05]: Over the limit memory handler.
> >
> 
> Hi, Rohit,
> 
> The patches are hard to follow - are they diff'ed with Naurp?
> At certain places I cannot figure out which function has changed.
> 

They are without p option so the function name is not there. Though
there is only one patch 02 of 05 that modifies existing code.  And that
too almost all single line changes are starting with container API
container_*  Please let me know if there is something specific that is
not clear.

I will send the next version of patches and I will include -p option as
well.

thanks,
-rohit

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/