From: sashiko-bot@kernel.org
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 4/4] net: drop_monitor: use drop_reason_lookup()
Date: Tue, 22 Sep 2026 10:15:57 +0000 [thread overview]
Message-ID: <20260922101558.BC1451F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260921101538.97286-10-johannes@sipsolutions.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] build: missing prototype for drop_reason_lookup() on !CONFIG_TRACEPOINTS
--
commit 052e9cafef9be2c8ee3e8254caa3827b7ac1f5b6
Author: Johannes Berg <johannes.berg@intel.com>
net: drop_monitor: use drop_reason_lookup()
This commit updates drop_monitor to use drop_reason_lookup() instead of
exporting the drop_reasons_by_subsys list. It unconditionally exposes the
drop_reason_lookup() function.
> diff --git a/include/net/dropreason.h b/include/net/dropreason.h
> index dc4a60130c09c..4680da5964ef7 100644
> --- a/include/net/dropreason.h
> +++ b/include/net/dropreason.h
[ ... ]
> -/* Note: due to dynamic registrations, access must be under RCU */
> -extern const struct drop_reason_list __rcu *
> -drop_reasons_by_subsys[SKB_DROP_REASON_SUBSYS_NUM];
> -
> #ifdef CONFIG_TRACEPOINTS
> const char *drop_reason_lookup(unsigned long long value);
[Severity: Low]
Will this cause a missing prototype build warning when CONFIG_TRACEPOINTS
is disabled?
The drop_reason_lookup() prototype in include/net/dropreason.h is conditionally
guarded by CONFIG_TRACEPOINTS.
> void drop_reason_show(struct seq_file *m);
[ ... ]
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index de294ce08a32c..a4ae26acc68c2 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
[ ... ]
> -EXPORT_SYMBOL(drop_reasons_by_subsys);
>
> -#ifdef CONFIG_TRACEPOINTS
> const char *drop_reason_lookup(unsigned long long value)
However, the function definition in net/core/skbuff.c is now compiled
unconditionally. This causes a -Wmissing-prototypes compiler warning when
compiling the kernel with CONFIG_TRACEPOINTS disabled.
Could this break builds where WERROR or W=1 is enabled?
> {
> unsigned long long subsys_id = value >> SKB_DROP_REASON_SUBSYS_SHIFT;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921101538.97286-6-johannes@sipsolutions.net?part=4
next prev parent reply other threads:[~2026-09-22 10:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 10:06 [PATCH v6 0/4] tracing: improve symbolic printing Johannes Berg
2026-09-21 10:06 ` [PATCH v6 1/4] tracing: add __print_sym() to replace __print_symbolic() Johannes Berg
2026-09-22 10:15 ` sashiko-bot
2026-09-21 10:06 ` [PATCH v6 2/4] tracing/timer: use __print_sym() Johannes Berg
2026-09-21 10:06 ` [PATCH v6 3/4] net: dropreason: use new __print_sym() in tracing Johannes Berg
2026-09-21 22:03 ` Matthieu Baerts
2026-09-21 22:23 ` Ilya Maximets
2026-09-21 22:36 ` Johannes Berg
2026-09-21 23:20 ` Johannes Berg
2026-09-22 9:01 ` Ilya Maximets
2026-09-22 9:03 ` Johannes Berg
2026-09-22 14:36 ` Adrián Moreno
2026-09-22 15:34 ` Aaron Conole
2026-09-28 15:21 ` Matthieu Baerts
2026-09-22 7:18 ` Antoine Tenart
2026-09-22 8:48 ` Ilya Maximets
2026-09-22 14:35 ` Adrián Moreno
2026-09-22 14:59 ` Johannes Berg
2026-09-21 10:06 ` [PATCH v6 4/4] net: drop_monitor: use drop_reason_lookup() Johannes Berg
2026-09-22 10:15 ` sashiko-bot [this message]
2026-09-21 21:59 ` [PATCH v6 0/4] tracing: improve symbolic printing Jakub Kicinski
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=20260922101558.BC1451F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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