** Changed in: procps (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when
This bug was fixed in the package procps - 2:3.3.16-1ubuntu2.1
---
procps (2:3.3.16-1ubuntu2.1) focal; urgency=medium
* Address slowness and crashes with large or unlimited stack limits
(LP: #1874824)
-- William 'jawn-smith' Wilson Wed, 24
Mar 2021 13:51:32 -0500
** Changed
This bug was fixed in the package procps - 2:3.3.16-5ubuntu2.1
---
procps (2:3.3.16-5ubuntu2.1) groovy; urgency=medium
* Address slowness and crashes with large or unlimited stack limits
(LP: #1874824)
-- William 'jawn-smith' Wilson Wed, 24
Mar 2021 10:09:08 -0500
** Changed
The verification passed for focal:
jawn-smith@focal-vm:~$ apt-cache policy procps
procps:
Installed: 2:3.3.16-1ubuntu2
Candidate: 2:3.3.16-1ubuntu2.1
Version table:
2:3.3.16-1ubuntu2.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
***
I tested procps/groovy-proposed,now 2:3.3.16-5ubuntu2.1 amd64. I have
repeated pgrep and pkill commands that caused the bug before. They do
work with the proposed package.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification
Ah, sorry, my mistake. I didn't think that pgrep.c would be used for a
different command. Now I see that pkill is a symlink to pgrep in
/usr/bin.
** Changed in: procps (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-groovy
--
Robie,
pgrep and pkill are sharing the same code. Essentially pkill runs pgrep
and then issues a kill signal to the resulting pid. Therefore this fix
applies to both pkill and pgrep. Additionally, the source of the problem
comes from the behavior of `sysconf(_SC_ARG_MAX)` changing in newer
> The problem is the same for other popular tools like pkill from the
same package.
The SRU uploads fix pgrep, but not pkill. Isn't pkill also affected?
Rather than fixing that in a separate SRU causing users to have to
update twice, should we be fixing both at the same time? Or are you
intending
I've sponsored the SRUs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when run without stack limit
Status in procps
** Patch added: "Groovy SRU"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484328/+files/lp1874824_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484329/+files/lp1874824_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
This bug was fixed in the package procps - 2:3.3.16-5ubuntu3
---
procps (2:3.3.16-5ubuntu3) hirsute; urgency=medium
* Address slowness and crashes with large or unlimited stack limits
(LP: #1874824)
-- William 'jawn-smith' Wilson Wed, 24
Mar 2021 10:09:08 -0500
** Changed
** Changed in: procps (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: procps (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: procps (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
I've sponsored this for hirsute but changed the package version to not
include the release number as this isn't an SRU for hirsute.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
The attachment "Hirsute debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
** Description changed:
+ [Impact]
+
+ - 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)
Attached is a patch to fix the issue in hirsute. Assuming this is
approved, I have also prepared the SRUs for focal and groovy.
** Patch added: "Hirsute debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5480543/+files/lp1874824_hirsute.debdiff
--
You
** Changed in: procps (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: procps (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: procps (Ubuntu Hirsute)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
FWIW, I was able to apply bb96fc4295 cleanly to the current 20.04
package (2:3.3.16-1ubuntu2) and it works for me.
apt-get -y source procps && cd procps-*
curl -fSsL -o debian/patches/sc_arg_max
https://gitlab.com/procps-ng/procps/-/commit/bb96fc4295.patch
echo sc_arg_max >>debian/patches/series
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: procps (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: procps (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
** Also affects: procps (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Hirsute)
Importance: Undecided
Status: Triaged
** Also affects: procps (Ubuntu Focal)
Importance: Undecided
Status: New
** Tags removed: rls-hh-incoming
--
** Tags added: fr-1174
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when run without stack limit
Status in procps
Patch available at https://gitlab.com/procps-
ng/procps/-/commit/bb96fc42956c9ed926a1b958ab715f8b4a663dec
** Tags added: bitesize patch rls-hh-incoming
** Changed in: procps (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when run without stack limit
Status in procps
Can the bug fix be applied for Ubuntu 21.04? Please.
On slow machines like a Raspberry 4 with stack limit 50 (Ubuntu
20.10), a single pgrep call takes 17 seconds!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in
It appeared today, after rebooting with the latest kernel, however I
have not updated procps since some time now and it was working before
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when run without stack limit
Status in procps
Even worse for Ubuntu 20.10 (procps 2:3.3.16-5ubuntu2). With a stack
limit of 50, almost 11 seconds for a simple pgrep; without
stacklimit, immediate crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in
The Arch Linux fix appeared in Manjaro. I can confirm that it works on
Manjaro machines.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error
** Changed in: procps (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when run
I installed procps-ng 3.3.16.49-ae4a myself on all our Ubuntu 20.04
computers. This fixed both problems, slow pgrep / pkill and crashing
pgrep / pkill.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
** Also affects: procps (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955697
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
Archlinux fixed this bug today, now in testing stage. Any news for
Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: procps (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
The problem is the same for other popular tools like pkill from the same
package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot
For the unlimited case, there is also Debian bug #955697
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955697
Those bug reports do not mention the massive slowdown linear in stack limit.
** Bug watch added: Debian Bug tracker #955697
37 matches
Mail list logo
