From: "tip-bot2 for Qianfeng Rong" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Qianfeng Rong <rongqianfeng@vivo.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] uprobes: Remove redundant __GFP_NOWARN
Date: Mon, 25 Aug 2025 10:24:30 -0000 [thread overview]
Message-ID: <175611747090.1420.3132265103580716698.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250805025000.346647-1-rongqianfeng@vivo.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: e173287b5d2119971fc329473a020171836d14c9
Gitweb: https://git.kernel.org/tip/e173287b5d2119971fc329473a020171836d14c9
Author: Qianfeng Rong <rongqianfeng@vivo.com>
AuthorDate: Tue, 05 Aug 2025 10:50:00 +08:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Thu, 21 Aug 2025 20:09:26 +02:00
uprobes: Remove redundant __GFP_NOWARN
Commit 16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT")
made GFP_NOWAIT implicitly include __GFP_NOWARN.
Therefore, explicit __GFP_NOWARN combined with GFP_NOWAIT
(e.g., `GFP_NOWAIT | __GFP_NOWARN`) is now redundant. Let's clean
up these redundant flags across subsystems.
No functional changes.
Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Oleg Nesterov <oleg@redhat.com>
Link: https://lore.kernel.org/r/20250805025000.346647-1-rongqianfeng@vivo.com
---
kernel/events/uprobes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index 4a194d7..996a810 100644
--- a/kernel/events/uprobes.c
+++ b/kernel/events/uprobes.c
@@ -1220,7 +1220,7 @@ build_map_info(struct address_space *mapping, loff_t offset, bool is_register)
* reclaim. This is optimistic, no harm done if it fails.
*/
prev = kmalloc(sizeof(struct map_info),
- GFP_NOWAIT | __GFP_NOMEMALLOC | __GFP_NOWARN);
+ GFP_NOWAIT | __GFP_NOMEMALLOC);
if (prev)
prev->next = NULL;
}
prev parent reply other threads:[~2025-08-25 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 2:50 [PATCH] " Qianfeng Rong
2025-08-05 11:33 ` Oleg Nesterov
2025-08-25 10:24 ` tip-bot2 for Qianfeng Rong [this message]
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=175611747090.1420.3132265103580716698.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rongqianfeng@vivo.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®