From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, rostedt@goodmis.org, vvs@openvz.org,
akpm@linux-foundation.org
Subject: [merged mm-stable] tracing-incorrect-isolate_mote_t-cast-in-mm_vmscan_lru_isolate.patch removed from -mm tree
Date: Thu, 19 May 2022 15:26:03 -0700 [thread overview]
Message-ID: <20220519222603.BBC36C385B8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: tracing: incorrect isolate_mote_t cast in mm_vmscan_lru_isolate
has been removed from the -mm tree. Its filename was
tracing-incorrect-isolate_mote_t-cast-in-mm_vmscan_lru_isolate.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Vasily Averin <vvs@openvz.org>
Subject: tracing: incorrect isolate_mote_t cast in mm_vmscan_lru_isolate
Date: Wed, 11 May 2022 12:46:53 +0300
Fixes following sparse warnings:
CHECK mm/vmscan.c
mm/vmscan.c: note: in included file (through
include/trace/trace_events.h, include/trace/define_trace.h,
include/trace/events/vmscan.h):
./include/trace/events/vmscan.h:281:1: sparse: warning:
cast to restricted isolate_mode_t
./include/trace/events/vmscan.h:281:1: sparse: warning:
restricted isolate_mode_t degrades to integer
Link: https://lkml.kernel.org/r/e85d7ff2-fd10-53f8-c24e-ba0458439c1b@openvz.org
Signed-off-by: Vasily Averin <vvs@openvz.org>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/trace/events/vmscan.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/include/trace/events/vmscan.h~tracing-incorrect-isolate_mote_t-cast-in-mm_vmscan_lru_isolate
+++ a/include/trace/events/vmscan.h
@@ -297,7 +297,7 @@ TRACE_EVENT(mm_vmscan_lru_isolate,
__field(unsigned long, nr_scanned)
__field(unsigned long, nr_skipped)
__field(unsigned long, nr_taken)
- __field(isolate_mode_t, isolate_mode)
+ __field(unsigned int, isolate_mode)
__field(int, lru)
),
@@ -308,7 +308,7 @@ TRACE_EVENT(mm_vmscan_lru_isolate,
__entry->nr_scanned = nr_scanned;
__entry->nr_skipped = nr_skipped;
__entry->nr_taken = nr_taken;
- __entry->isolate_mode = isolate_mode;
+ __entry->isolate_mode = (__force unsigned int)isolate_mode;
__entry->lru = lru;
),
_
Patches currently in -mm which might be from vvs@openvz.org are
cleanup-for-tracing-incorrect-gfp_t-conversion.patch
cleanup-for-percpu-improve-percpu_alloc_percpu-event-trace.patch
reply other threads:[~2022-05-19 22:26 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=20220519222603.BBC36C385B8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=vvs@openvz.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.