From: Jakub Kicinski <kuba@kernel.org>
To: Yunseong Kim <yskelg@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Sasha Levin <sashal@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Taehee Yoo <ap420073@gmail.com>,
Pedro Tammela <pctammela@mojatatu.com>,
Austin Kim <austindh.kim@gmail.com>,
MichelleJin <shjy180909@gmail.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
netdev@vger.kernel.org, ppbuk5246@gmail.com,
Yeoreum Yun <yeoreum.yun@arm.com>
Subject: Re: [PATCH] tracing/net_sched: NULL pointer dereference in perf_trace_qdisc_reset()
Date: Wed, 3 Jul 2024 19:18:35 -0700 [thread overview]
Message-ID: <20240703191835.2cc2606f@kernel.org> (raw)
In-Reply-To: <20240702180146.5126-2-yskelg@gmail.com>
On Wed, 3 Jul 2024 03:01:47 +0900 Yunseong Kim wrote:
> Support backports for stable version. There are two places where null
> deref could happen before
> commit 2c92ca849fcc ("tracing/treewide: Remove second parameter of __assign_str()")
> Link: https://lore.kernel.org/linux-trace-kernel/20240516133454.681ba6a0@rorschach.local.home/
>
> I've checked +v6.1.82 +v6.6.22 +v6.7.10, +v6.8, +6.9, this version need
> to be applied, So, I applied the patch, tested it again, and confirmed
> working fine.
You're missing the customary "[ Upstream commit <upstream commit> ]"
line, not sure Greg will pick this up.
next prev parent reply other threads:[~2024-07-04 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 18:01 [PATCH] tracing/net_sched: NULL pointer dereference in perf_trace_qdisc_reset() Yunseong Kim
2024-07-04 2:18 ` Jakub Kicinski [this message]
2024-07-04 9:32 ` Greg Kroah-Hartman
2024-07-04 11:16 ` Yunseong Kim
2024-07-04 11:54 ` Greg Kroah-Hartman
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=20240703191835.2cc2606f@kernel.org \
--to=kuba@kernel.org \
--cc=ap420073@gmail.com \
--cc=austindh.kim@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=ppbuk5246@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=shjy180909@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yeoreum.yun@arm.com \
--cc=yskelg@gmail.com \
/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.