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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat, 29 Oct 2022 06:30:21 +0000
To:     Alex Elder <>
Subject: Re: [PATCH net-next 0/7] net: ipa: start adding IPA v5.0 functionality


This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <>:

On Thu, 27 Oct 2022 07:26:25 -0500 you wrote:
> The biggest change for IPA v5.0 is that it supports more than 32
> endpoints.  However there are two other unrelated changes:
>   - The STATS_TETHERING memory region is not required
>   - Filter tables no longer support a "global" filter
> Beyond this, refactoring some code makes supporting more than 32
> endpoints (in an upcoming series) easier.  So this series includes
> a few other changes (not in this order):
>   - The maximum endpoint ID in use is determined during config
>   - Loops over all endpoints only involve those in use
>   - Endpoints IDs and their directions are checked for validity
>     differently to simplify comparison against the maximum
> [...]

Here is the summary with links:
  - [net-next,1/7] net: ipa: define IPA v5.0
  - [net-next,2/7] net: ipa: change an IPA v5.0 memory requirement
  - [net-next,3/7] net: ipa: no more global filtering starting with IPA v5.0
  - [net-next,4/7] net: ipa: more completely check endpoint validity
    (no matching commit)
  - [net-next,5/7] net: ipa: refactor endpoint loops
  - [net-next,6/7] net: ipa: determine the maximum endpoint ID
  - [net-next,7/7] net: ipa: record and use the number of defined endpoint IDs

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists