public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] denied resource overstep... for RLIMIT_MEMLOCK
Date: Sat, 17 Jan 2009 11:06:42 -0800	[thread overview]
Message-ID: <49bf44f10901171106y739a77dfq92ee52529b17df83@mail.gmail.com> (raw)
In-Reply-To: <49703C1A.20802.11B6ED58@pageexec.freemail.hu>

>> One of my Blu-Ray rips won't play and there is a steady stream of
>> "Error while decoding frame!" messages in mplayer's output when I try.
>>  I just noticed that each time I try to play the movie, I get another
>> one of these in dmesg:
>>
>> grsec: denied resource overstep by requesting 135168 for
>> RLIMIT_MEMLOCK against limit 32768 for /usr/bin/mplayer[mplayer:22122]
>> uid/euid:1000/1000 gid/egid:100/100, parent /bin/bash[bash:22095]
>> uid/euid:1000/1000 gid/egid:100/100
>
> it's just a report that mplayer wanted to lock more memory than
> you allowed, or rather, what the kernel allows by default. ulimit(1)
> and related things are your friend.
>
>> paxctl -m /usr/bin/mplayer
>>
>> but it doesn't seem to make any difference.
>
> actually, that one is needed for certain win32 codecs.

I'm on amd64 anyway and mplayer-bin doesn't seem to be maintained these days.

>>  Does anyone know how to
>> fix this?  How can I undo what I did with the above paxctl command
>> since it doesn't seem to be helping?
>
> man paxctl would tell you if you looked ;).

Thanks, it's 'paxctl -M /usr/bin/mplayer'.

- Grant



  reply	other threads:[~2009-01-17 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  1:55 [gentoo-hardened] denied resource overstep... for RLIMIT_MEMLOCK Grant
2009-01-16  2:05 ` [gentoo-hardened] " Grant
2009-01-16  6:49   ` pageexec
2009-01-16  6:49 ` [gentoo-hardened] " pageexec
2009-01-17 19:06   ` Grant [this message]
2009-01-17 22:27     ` pageexec
2009-01-18  0:20       ` Manuel Leithner
2009-01-18  0:08         ` pageexec
2009-01-18  4:08           ` Grant
2009-01-18  0:43         ` Gordon Malm

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=49bf44f10901171106y739a77dfq92ee52529b17df83@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --cc=gentoo-hardened@lists.gentoo.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