Opened at 2011-06-17T04:46:57Z

Closed at 2011-06-20T05:15:03Z

#1421 closed enhancement (invalid)

increase_rlimits() tries to set RLIMIT_CORE high, which grsec disallows

Reported by: zooko Owned by: somebody
Priority: minor Milestone: undecided
Component: code Version: 1.8.2
Keywords: grsec Cc:
Launchpad Bug:

Description

Originally reported in #982 by ioerror:

Grsec disallows a resource overstep when tahoe requests 4196256 for RLIMIT_CORE. To get tahoe started, you'll need to add the following to the init.d script: 

ulimit -c 4196256

But, when I read the source code of increase_rlimits()​ I don't see any evidence that we deliberately set RLIMIT_CORE. (We certainly never intended to.)

So, is it that calling resource.getrlimit(resource.RLIMIT_NOFILE) is also setting RLIMIT_CORE? Perhaps this is a bug in the Python standard library. Could someone with grsecurity installed please reproduce this issue and show the complete error message?

Change History (3)

comment:1 Changed at 2011-06-17T05:02:44Z by zooko

  • Keywords grsec added; grsecurity removed

comment:2 Changed at 2011-06-17T11:45:32Z by zooko

I posted to the grsec mailing list asking about this: ​http://grsecurity.net/pipermail/grsecurity/2011-June/001083.html

comment:3 Changed at 2011-06-20T05:15:03Z by zooko

  • Resolution set to invalid
  • Status changed from new to closed

Brad Spengler ​posted to the grsec mailing list that it was probably due to the other issue (#982) that the process was attempting to dump core, and that the RLIMIT_CORE is probably set to that value by default, so closing this as not-an-issue.

Note: See TracTickets for help on using tickets.