From: Chris Wright <chrisw@osdl.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Chris Wright <chrisw@osdl.org>,
akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH] mips default mlock limit fix
Date: Thu, 20 Jan 2005 10:13:51 -0800 [thread overview]
Message-ID: <20050120101351.J24171@build.pdx.osdl.net> (raw)
In-Reply-To: <20050120160005.GA5672@linux-mips.org>; from ralf@linux-mips.org on Thu, Jan 20, 2005 at 05:00:05PM +0100
* Ralf Baechle (ralf@linux-mips.org) wrote:
> On Wed, Jan 19, 2005 at 05:59:45PM -0800, Chris Wright wrote:
>
> > Mips RLIMIT_MEMLOCK incorrectly defaults to unlimited, it was confused
> > with RLIMIT_NPROC. Found while consolidating resource.h headers.
>
> Thanks, I applied a recent change off by one line. To avoid this I've
> changed the code to use named initializers, see
>
> http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-cvs-patches&i=95f18dfc8e770c9885b796a676935677%40NO-ID-FOUND.mhonarc.org
That works too. I made a similar change in the consolidation patch. This
was just meant to be a very simple stop gap fix, while the consolidation
bits bake in -mm before they go to Linus. I prefer to leave it as is,
only so I don't have to respin the patches, but it's not that big a deal.
Either way, Linus should pick up one of the mips fixes.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-01-20 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 1:59 [PATCH] mips default mlock limit fix Chris Wright
2005-01-20 16:00 ` Ralf Baechle
2005-01-20 18:13 ` Chris Wright [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=20050120101351.J24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@osdl.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.