mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Mark Haverkamp <markh@osdl.org>,
	Openais List <openais@lists.osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 kernel oops with openais
Date: Fri, 29 Oct 2004 16:57:06 -0700	[thread overview]
Message-ID: <1099094226.1207.13.camel@persist.az.mvista.com> (raw)
In-Reply-To: <20041029164551.U2357@build.pdx.osdl.net>

Chris

The change was that from 2.6.8 to 2.6.9 the rlimit for memlock was
changed from infinity to 32k (and at the same time, normal users are now
allowed to use mlockall if they dont have alot of memory to mlock).  I
fixed up the openais code by doing something evil from uid 0 like:

       struct rlimit rlimit;

        rlimit.rlim_cur = RLIM_INFINITY;
        rlimit.rlim_max = RLIM_INFINITY;
        setrlimit (RLIMIT_MEMLOCK, &rlimit);

Thanks
-steve

On Fri, 2004-10-29 at 16:45, Chris Wright wrote:
> * Steven Dake (sdake@mvista.com) wrote:
> > The use case is this (on 2.6.9):
> > 
> > task starts as uid 0
> > task calls mlockall
> > task allocates several mb of ram
> > task drops root privs to non prived uid
> > further memory allocations fail
> 
> What's the RLIMIT_MEMLOCK?
> 
> thanks,
> -chris


  reply	other threads:[~2004-10-30  0:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 22:51 Steven Dake
2004-10-29 23:08 ` Mark Haverkamp
2004-10-29 23:16   ` Steven Dake
2004-10-29 23:39     ` Chris Wright
2004-10-29 23:44       ` Steven Dake
2004-10-29 23:45         ` Chris Wright
2004-10-29 23:57           ` Steven Dake [this message]
2004-10-30  0:01             ` Chris Wright
2004-10-30  0:11               ` Steven Dake
2004-10-30  0:19                 ` Chris Wright
2004-10-30  0:42                 ` Lee Revell
2004-10-29 23:42   ` Steven Dake

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=1099094226.1207.13.camel@persist.az.mvista.com \
    --to=sdake@mvista.com \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@osdl.org \
    --cc=openais@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®