netdev - Re: [PATCH net-next v3 00/16] Handle multi chain hardware misses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 19 Feb 2020 16:12:55 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     saeedm@...lanox.com
Cc:     ozsh@...lanox.com, vladbu@...lanox.com, paulb@...lanox.com,
        jiri@...lanox.com, kuba@...nel.org, netdev@...r.kernel.org,
        roid@...lanox.com
Subject: Re: [PATCH net-next v3 00/16] Handle multi chain hardware misses

From: Saeed Mahameed <saeedm@...lanox.com>
Date: Wed, 19 Feb 2020 02:43:08 +0000

> On Sun, 2020-02-16 at 12:01 +0200, Paul Blakey wrote:
>> Hi David/Jakub/Saeed,
>> 
>> TC multi chain configuration can cause offloaded tc chains to miss in
>> hardware after jumping to some chain. In such cases the software
>> should
>> continue from the chain that was missed in hardware, as the hardware
>> may have
>> manipulated the packet and updated some counters.
>> 
> 
> [...]
> 
>> Note that miss path handling of multi-chain rules is a required
>> infrastructure
>> for connection tracking hardware offload. The connection tracking
>> offload
>> series will follow this one.
>> 
> 
> Hi Dave, 
> 
> As was agreed, i will apply this series and the two to follow to a side
> branch until all the connection tracking offloads patchsets are posted
> by Paul and reviewed/acked.
> 
> in case of no objection i will apply this patchset to allow Paul to
> move forward with the other two connection tracking patchsets.

I have no objection to this series, can you setup a pull request with this
series in it that I can pull from into net-next?

Thanks.