From: Florian Fainelli <f.fainelli@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com,
linux-kernel@vger.kernel.org, opendmb@gmail.com
Subject: Re: [PATCH net v2 0/3] net: dsa: bcm_sf2: CFP fixes
Date: Wed, 16 May 2018 11:15:37 -0700 [thread overview]
Message-ID: <e88ff455-2072-c885-e64b-0f2bf91420a4@gmail.com> (raw)
In-Reply-To: <20180516.141218.827550466386531999.davem@davemloft.net>
On 05/16/2018 11:12 AM, David Miller wrote:
> From: Florian Fainelli <f.fainelli@gmail.com>
> Date: Tue, 15 May 2018 16:01:22 -0700
>
>> This patch series fixes a number of usability issues with the SF2 Compact Field
>> Processor code:
>>
>> - we would not be properly bound checking the location when we let the kernel
>> automatically place rules with RX_CLS_LOC_ANY
>>
>> - when using IPv6 rules and user space specifies a location identifier we
>> would be off by one in what the chain ID (within the Broadcom tag) indicates
>>
>> - it would be possible to delete one of the two slices of an IPv6 while leaving
>> the other one programming leading to various problems
>
> Series applied, thanks.
>
> Queue up for -stable?
Yes please!
--
Florian
next prev parent reply other threads:[~2018-05-16 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 23:01 [PATCH net v2 0/3] net: dsa: bcm_sf2: CFP fixes Florian Fainelli
2018-05-15 23:01 ` [PATCH net v2 1/3] net: dsa: bcm_sf2: Fix RX_CLS_LOC_ANY overwrite for last rule Florian Fainelli
2018-05-15 23:01 ` [PATCH net v2 2/3] net: dsa: bcm_sf2: Fix IPv6 rules and chain ID Florian Fainelli
2018-05-15 23:01 ` [PATCH net v2 3/3] net: dsa: bcm_sf2: Fix IPv6 rule half deletion Florian Fainelli
2018-05-16 18:12 ` [PATCH net v2 0/3] net: dsa: bcm_sf2: CFP fixes David Miller
2018-05-16 18:15 ` Florian Fainelli [this message]
2018-05-16 18:18 ` David Miller
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=e88ff455-2072-c885-e64b-0f2bf91420a4@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=vivien.didelot@savoirfairelinux.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