From: Changqing Li <changqing.li@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] procps: upgrade from 4.0.5 to 4.0.6
Date: Tue, 24 Feb 2026 09:47:47 +0800 [thread overview]
Message-ID: <20260224014748.3336195-1-changqing.li@windriver.com> (raw)
Remove patch top_large_pid_fix.patch, already in 4.0.6
Signed-off-by: Changqing Li <changqing.li@windriver.com>
---
.../procps/procps/top_large_pid_fix.patch | 52 -------------------
.../{procps_4.0.5.bb => procps_4.0.6.bb} | 3 +-
2 files changed, 1 insertion(+), 54 deletions(-)
delete mode 100644 meta/recipes-extended/procps/procps/top_large_pid_fix.patch
rename meta/recipes-extended/procps/{procps_4.0.5.bb => procps_4.0.6.bb} (97%)
diff --git a/meta/recipes-extended/procps/procps/top_large_pid_fix.patch b/meta/recipes-extended/procps/procps/top_large_pid_fix.patch
deleted file mode 100644
index d7e3141e06..0000000000
--- a/meta/recipes-extended/procps/procps/top_large_pid_fix.patch
+++ /dev/null
@@ -1,52 +0,0 @@
-From f21fc624d960d12afa399af7333d4f9193fb2ffb Mon Sep 17 00:00:00 2001
-From: Jim Warner <james.warner@comcast.net>
-Date: Tue, 16 Sep 2025 12:00:00 -0500
-Subject: [PATCH] library: avoid possible segmentation fault, <pids> api
-Upstream-Status: Backport
-[https://gitlab.com/procps-ng/procps/-/commit/5461b50b1a85c5e556c4cd2739ca8ffdbc69399a]
-
-In the issue referenced below, that SEGV was caused by
-passing a '-1' pid to the procps_pids_select function.
-That value, in turn, is caused by providing a LONG_MAX
-or greater number for what was assigned to an integer.
-
-So, this commit will help ensure we avoid a match when
-we should fail plus skip some unproductive libc calls.
-
-[ the same problem occurs in that old 3.3.17 library ]
-
-Reference(s):
-https://gitlab.com/procps-ng/procps/-/issues/394
-
-Signed-off-by: Jim Warner <james.warner@comcast.net>
-Signed-off-by: Amaury Couderc <amaury.couderc@est.tech>
-
----
- library/readproc.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/library/readproc.c b/library/readproc.c
-index 2dfe4c9e..d0e039bf 100644
---- a/library/readproc.c
-+++ b/library/readproc.c
-@@ -1434,7 +1434,7 @@ static int listed_nextpid (PROCTAB *PT, proc_t *p) {
- pid_t pid = *(PT->pids)++;
- char *path = PT->path;
-
-- if (pid) {
-+ if (pid > 0) {
- snprintf(path, PROCPATHLEN, "/proc/%d", pid);
- p->tid = p->tgid = pid; // this tgid may be a huge fib |
-
-@@ -1546,7 +1546,7 @@ PROCTAB *openproc(unsigned flags, ...) {
- did_stat = 1;
- }
- PT->taskdir = NULL;
-- PT->taskdir_user = -1;
-+ PT->taskdir_user = -2;
- PT->taskfinder = simple_nexttid;
- PT->taskreader = simple_readtask;
-
---
-2.43.0
-
diff --git a/meta/recipes-extended/procps/procps_4.0.5.bb b/meta/recipes-extended/procps/procps_4.0.6.bb
similarity index 97%
rename from meta/recipes-extended/procps/procps_4.0.5.bb
rename to meta/recipes-extended/procps/procps_4.0.6.bb
index 0e0e06f0d2..168027077b 100644
--- a/meta/recipes-extended/procps/procps_4.0.5.bb
+++ b/meta/recipes-extended/procps/procps_4.0.6.bb
@@ -14,9 +14,8 @@ inherit autotools gettext pkgconfig update-alternatives
SRC_URI = "git://gitlab.com/procps-ng/procps.git;protocol=https;branch=master;tag=v${PV} \
file://sysctl.conf \
- file://top_large_pid_fix.patch \
"
-SRCREV = "f46b2f7929cdfe2913ed0a7f585b09d6adbf994e"
+SRCREV = "4dafddf4c3f4646caa517f039a2307e92657ec93"
# Upstream has a custom autogen.sh which invokes po/update-potfiles as they
# don't ship a po/POTFILES.in (which is silly). Without that file gettext
--
2.34.1
next reply other threads:[~2026-02-24 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:47 Changqing Li [this message]
2026-02-24 1:47 ` [PATCH 2/2] procps: support ptest when TCLIBC is glibc Changqing Li
2026-02-26 13:13 ` [OE-core] " Ross Burton
2026-02-27 6:17 ` Changqing Li
2026-02-27 6:49 ` [PATCH V2] " Changqing Li
2026-03-05 15:16 ` [OE-core] " Ross Burton
2026-03-06 4:05 ` [PATCH V3] " Changqing Li
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=20260224014748.3336195-1-changqing.li@windriver.com \
--to=changqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.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