From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, daniel@iogearbox.net, jiri@resnulli.us,
oss-drivers@netronome.com
Subject: Re: [PATCH net 0/2] cls_bpf: fix offload state tracking with block callbacks
Date: Wed, 20 Dec 2017 13:32:47 -0500 (EST) [thread overview]
Message-ID: <20171220.133247.762420942850262542.davem@davemloft.net> (raw)
In-Reply-To: <20171219213214.1084-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue, 19 Dec 2017 13:32:12 -0800
> After introduction of block callbacks classifiers can no longer track
> offload state. cls_bpf used to do that in an attempt to move common
> code from drivers to the core. Remove that functionality and fix
> drivers.
>
> The user-visible bug this is fixing is that trying to offload a second
> filter would trigger a spurious DESTROY and in turn disable the already
> installed one.
Series applied, thanks for the heads up about the net-next conflict.
prev parent reply other threads:[~2017-12-20 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 21:32 [PATCH net 0/2] cls_bpf: fix offload state tracking with block callbacks Jakub Kicinski
2017-12-19 21:32 ` [PATCH net 1/2] cls_bpf: fix offload assumptions after callback conversion Jakub Kicinski
2017-12-20 6:05 ` Jiri Pirko
2017-12-19 21:32 ` [PATCH net 2/2] nfp: bpf: keep track of the offloaded program Jakub Kicinski
2017-12-20 11:33 ` [oss-drivers] [PATCH net 0/2] cls_bpf: fix offload state tracking with block callbacks Quentin Monnet
2017-12-20 18:32 ` 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=20171220.133247.762420942850262542.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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