[Bug 1874824] Please test proposed package

Robie Basak 1874824 at bugs.launchpad.net
Wed Apr 7 16:36:52 UTC 2021

Hello Sven, or anyone else affected,

Accepted procps into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.16-5ubuntu2.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: procps (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.

  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Focal:
  Fix Committed
Status in procps source package in Groovy:
  Fix Committed
Status in procps source package in Hirsute:
  Fix Released
Status in procps package in Debian:

Bug description:

    - Users who have ulimit set high would see either slow
      or failed pgrep and pkill commands
    - Users who have ulimit set to unlimited would see
      failed pgrep and pkill commands
    - This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
      changed with a newer version of the kernel.

  [Test Case]

    - set the ulimit to unlimited by running `ulimit -S -s unlimited`
    - run `pgrep bash` to see that the "cannot allocate" error is
       printed and the command has failed.

  [Where Problems Could Occur]

    - We have set upper and lower limits on the size of the malloc, but
      if further kernel versions break the call to sysconf in
      unexpected ways we could still see problems.

  [Original Description]

  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 500000), pgrep is
  very slow:

  > time pgrep vim
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

    Installed: 2:3.3.16-1ubuntu2
    500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:

More information about the Ubuntu-sponsors mailing list