netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: aring@mojatatu.com
Cc: yotam.gi@gmail.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, yuvalm@mellanox.com, netdev@vger.kernel.org,
	kernel@mojatatu.com
Subject: Re: [PATCHv4 net 0/3] net: sched: ife: malformed ife packet fixes
Date: Sun, 22 Apr 2018 21:12:45 -0400 (EDT)	[thread overview]
Message-ID: <20180422.211245.1237510032969219473.davem@davemloft.net> (raw)
In-Reply-To: <20180420191505.27633-1-aring@mojatatu.com>

From: Alexander Aring <aring@mojatatu.com>
Date: Fri, 20 Apr 2018 15:15:02 -0400

> As promised at netdev 2.2 tc workshop I am working on adding scapy support for
> tdc testing. It is still work in progress. I will submit the patches to tdc
> later (they are not in good shape yet). The good news is I have been able to
> find bugs which normal packet testing would not be able to find.
> With fuzzy testing I was able to craft certain malformed packets that IFE
> action was not able to deal with. This patch set fixes those bugs.

Series applied and queued up for -stable.

      parent reply	other threads:[~2018-04-23  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 19:15 [PATCHv4 net 0/3] net: sched: ife: malformed ife packet fixes Alexander Aring
2018-04-20 19:15 ` [PATCHv4 net 1/3] net: sched: ife: signal not finding metaid Alexander Aring
2018-04-20 19:15 ` [PATCHv4 net 2/3] net: sched: ife: handle malformed tlv length Alexander Aring
2018-04-20 19:15 ` [PATCHv4 net 3/3] net: sched: ife: check on metadata length Alexander Aring
2018-04-23  1:12 ` David Miller [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=20180422.211245.1237510032969219473.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=aring@mojatatu.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yotam.gi@gmail.com \
    --cc=yuvalm@mellanox.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).