From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v6 0/4] tracing: improve symbolic printing
Date: Mon, 21 Sep 2026 14:59:50 -0700 [thread overview]
Message-ID: <20260921145950.62c4a669@kernel.org> (raw)
In-Reply-To: <20260921101538.97286-6-johannes@sipsolutions.net>
On Mon, 21 Sep 2026 12:06:31 +0200 Johannes Berg wrote:
> Hi,
>
> Alright, this took forever, it never quite made it to the top of
> my list ... Two years ago Steven reported a crash in v5, and now
> I finally really looked into it and realized it was because of
> section placement.
Breaks ovs test which tries to catch the drop reasons:
https://netdev-ctrl.bots.linux.dev/logs/vmksft/net-dbg/results/833743/10-openvswitch-sh/stdout
prev parent reply other threads:[~2026-09-21 21:59 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
2026-09-21 21:59 ` Jakub Kicinski [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=20260921145950.62c4a669@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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.