From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, alex_y_xu@yahoo.ca,
akpm@linux-foundation.org
Subject: [-] mm-smaps_rollup-return-empty-file-for-kthreads-instead-of-esrch.patch removed from -mm tree
Date: Wed, 27 Apr 2022 13:35:28 -0700 [thread overview]
Message-ID: <20220427203529.67C9EC385A7@smtp.kernel.org> (raw)
The patch titled
Subject: mm/smaps_rollup: return empty file for kthreads instead of ESRCH
has been removed from the -mm tree. Its filename was
mm-smaps_rollup-return-empty-file-for-kthreads-instead-of-esrch.patch
This patch was dropped because of indecision
------------------------------------------------------
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Subject: mm/smaps_rollup: return empty file for kthreads instead of ESRCH
This restores the behavior prior to 258f669e7e88 ("mm:
/proc/pid/smaps_rollup: convert to single value seq_file"), making it once
again consistent with maps and smaps, and allowing patterns like awk
'$1=="Anonymous:"{x+=$2}END{print x}' /proc/*/smaps_rollup to work.
Searching all Debian packages for "smaps_rollup" did not find any programs
which would be affected by this change.
Link: https://lkml.kernel.org/r/20220413211357.26938-1-alex_y_xu@yahoo.ca
Fixes: 258f669e7e88 ("mm: /proc/pid/smaps_rollup: convert to single value seq_file")
Signed-off-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/proc/task_mmu.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--- a/fs/proc/task_mmu.c~mm-smaps_rollup-return-empty-file-for-kthreads-instead-of-esrch
+++ a/fs/proc/task_mmu.c
@@ -883,10 +883,8 @@ static int show_smaps_rollup(struct seq_
return -ESRCH;
mm = priv->mm;
- if (!mm || !mmget_not_zero(mm)) {
- ret = -ESRCH;
+ if (!mm || !mmget_not_zero(mm))
goto out_put_task;
- }
memset(&mss, 0, sizeof(mss));
_
Patches currently in -mm which might be from alex_y_xu@yahoo.ca are
reply other threads:[~2022-04-27 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220427203529.67C9EC385A7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=alex_y_xu@yahoo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.