From: Ido Schimmel <idosch@idosch.org>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
simon.horman@corigine.com
Subject: Re: [PATCH net-next v5 3/5] net/sched: act_pedit: check static offsets a priori
Date: Tue, 25 Apr 2023 16:36:12 +0300 [thread overview]
Message-ID: <ZEfXTLmTZUzVA4m4@shredder> (raw)
In-Reply-To: <f331c935-85b6-5e1a-d01b-57041aa12419@mojatatu.com>
On Tue, Apr 25, 2023 at 09:27:32AM -0300, Pedro Tammela wrote:
> Can you run the syzkaller corpus with the following patch?
The C reproducer allows anyone to test a fix without any special
dependencies. The reproducer triggers the issue without the fix and does
not trigger the issue with the fix.
Thanks
next prev parent reply other threads:[~2023-04-25 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 21:25 [PATCH net-next v5 0/5] net/sched: act_pedit: minor improvements Pedro Tammela
2023-04-21 21:25 ` [PATCH net-next v5 1/5] net/sched: act_pedit: use NLA_POLICY for parsing 'ex' keys Pedro Tammela
2023-04-22 8:17 ` Simon Horman
2023-04-21 21:25 ` [PATCH net-next v5 2/5] net/sched: act_pedit: use extack in 'ex' parsing errors Pedro Tammela
2023-04-21 21:25 ` [PATCH net-next v5 3/5] net/sched: act_pedit: check static offsets a priori Pedro Tammela
2023-04-25 12:13 ` Ido Schimmel
2023-04-25 12:27 ` Pedro Tammela
2023-04-25 13:36 ` Ido Schimmel [this message]
2023-04-21 21:25 ` [PATCH net-next v5 4/5] net/sched: act_pedit: remove extra check for key type Pedro Tammela
2023-04-21 21:25 ` [PATCH net-next v5 5/5] net/sched: act_pedit: rate limit datapath messages Pedro Tammela
2023-04-23 17:40 ` [PATCH net-next v5 0/5] net/sched: act_pedit: minor improvements patchwork-bot+netdevbpf
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=ZEfXTLmTZUzVA4m4@shredder \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=simon.horman@corigine.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).