From: Jakub Kicinski <kuba@kernel.org>
To: Jun Nie <jun.nie@linaro.org>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net_sched: ematch: reject invalid data
Date: Mon, 12 Dec 2022 19:38:57 -0800 [thread overview]
Message-ID: <20221212193857.3656ae96@kernel.org> (raw)
In-Reply-To: <20221213012023.673544-1-jun.nie@linaro.org>
On Tue, 13 Dec 2022 09:20:23 +0800 Jun Nie wrote:
> Change-Id: Id2411e5ddcf3091ba3f37bddd722eac051bc9d57
> Reported-by: syzbot+963f7637dae8becc038f@syzkaller.appspotmail.com
Please repost with the following changes:
- no gerrit change-id
- [PATCH net] in the subject
- Fixes tag added
prev parent reply other threads:[~2022-12-13 3:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 1:20 [PATCH] net_sched: ematch: reject invalid data Jun Nie
2022-12-13 3:38 ` 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=20221212193857.3656ae96@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=jun.nie@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).