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:	Fri, 19 Sep 2008 13:14:05 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	balbir@...ux.vnet.ibm.com
Cc:	linux-mm@...ck.org, skumar@...ux.vnet.ibm.com,
	yamamoto@...inux.co.jp, menage@...gle.com, lizf@...fujitsu.com,
	linux-kernel@...r.kernel.org, xemul@...nvz.org,
	kamezawa.hiroyu@...fujitsu.com, mingo@...e.hu
Subject: Re: [-mm][PATCH 4/4] Add memrlimit controller accounting and
 control (v4)

On Thu, 18 Sep 2008 23:38:23 -0700
Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:

> * Andrew Morton <akpm@...ux-foundation.org> [2008-09-18 13:54:30]:
> 
> > On Wed, 14 May 2008 18:39:51 +0530
> > Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
> > 
> > > This patch adds support for accounting and control of virtual address space
> > > limits.
> > 
> > 
> > Large changes in linux-next's arch/x86/kernel/ptrace.c caused damage to
> > the memrlimit patches.
> > 
> > I decided to retain the patches because it looks repairable.  The
> > problem is this reject from
> > memrlimit-add-memrlimit-controller-accounting-and-control.patch:
> >
> 
> Andrew,
> 
> I could not apply mmotm to linux-next (both downloaded right now).

mmotm includes linux-next.patch.  mmotm is based upon the most recent
2.6.x-rcy.

This is the only way to do it - I often have to change linux-next.patch
due to rejects and it's unreasonable to expect people to base off the
same version of linux-next as I did.

> I
> applied the patches one-by-one resolving differences starting from #mm
> in the series file.
> 
> Here is my fixed version of the patch, I compiled the patch, but could
> not run it, since I could not create the full series of applied
> patches. I compiled arch/x86/kernel/ds.o and ptrace.o. I've included
> the patch below, please let me know if the code looks OK (via review)
> and the patch applies. I'll test it once I can resonably resolve all
> conflicts between linux-next and mmotm.

OK, we'll give it a shot, thanks.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ