* [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack
@ 2023-01-24 11:54 Leon Romanovsky
2023-01-25 19:01 ` Jakub Kicinski
2023-01-27 0:50 ` patchwork-bot+netdevbpf
0 siblings, 2 replies; 4+ messages in thread
From: Leon Romanovsky @ 2023-01-24 11:54 UTC (permalink / raw)
To: David S . Miller, Jakub Kicinski, Steffen Klassert
Cc: Andy Gospodarek, Ayush Sawal, Eric Dumazet, Herbert Xu,
intel-wired-lan, Jay Vosburgh, Jesse Brandeburg, Jonathan Corbet,
linux-doc, linux-kernel, netdev, oss-drivers, Paolo Abeni,
Raju Rangoju, Saeed Mahameed, Simon Horman, Tony Nguyen,
Veaceslav Falico
Changelog
v1:
* Fixed rebase errors in mlx5 and cxgb4 drivers
* Fixed previously existed typo in nfp driver
* Added Simon's ROB
* Removed my double SOB tags
v0: https://lore.kernel.org/all/cover.1674481435.git.leon@kernel.org
---------------------------------------------------------------------------
Hi,
This series continues effort started by Sabrina to return XFRM configuration
errors through extack. It allows for user space software stack easily present
driver failure reasons to users.
As a note, Intel drivers have a path where extack is equal to NULL, and error
prints won't be available in current patchset. If it is needed, it can be
changed by adding special to Intel macro to print to dmesg in case of
extack == NULL.
Thanks
Leon Romanovsky (10):
xfrm: extend add policy callback to set failure reason
net/mlx5e: Fill IPsec policy validation failure reason
xfrm: extend add state callback to set failure reason
net/mlx5e: Fill IPsec state validation failure reason
netdevsim: Fill IPsec state validation failure reason
nfp: fill IPsec state validation failure reason
ixgbevf: fill IPsec state validation failure reason
ixgbe: fill IPsec state validation failure reason
bonding: fill IPsec state validation failure reason
cxgb4: fill IPsec state validation failure reason
Documentation/networking/xfrm_device.rst | 4 +-
drivers/net/bonding/bond_main.c | 10 +-
.../net/ethernet/chelsio/cxgb4/cxgb4_main.c | 8 +-
.../inline_crypto/ch_ipsec/chcr_ipsec.c | 34 +++---
.../net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 27 ++---
drivers/net/ethernet/intel/ixgbevf/ipsec.c | 21 ++--
.../mellanox/mlx5/core/en_accel/ipsec.c | 103 ++++++++----------
.../net/ethernet/netronome/nfp/crypto/ipsec.c | 41 +++----
drivers/net/netdevsim/ipsec.c | 14 +--
include/linux/netdevice.h | 4 +-
net/xfrm/xfrm_device.c | 9 +-
net/xfrm/xfrm_state.c | 2 +-
12 files changed, 137 insertions(+), 140 deletions(-)
--
2.39.1
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack
2023-01-24 11:54 [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack Leon Romanovsky
@ 2023-01-25 19:01 ` Jakub Kicinski
2023-01-26 9:43 ` Steffen Klassert
2023-01-27 0:50 ` patchwork-bot+netdevbpf
1 sibling, 1 reply; 4+ messages in thread
From: Jakub Kicinski @ 2023-01-25 19:01 UTC (permalink / raw)
To: Leon Romanovsky
Cc: David S . Miller, Steffen Klassert, Andy Gospodarek, Ayush Sawal,
Eric Dumazet, Herbert Xu, intel-wired-lan, Jay Vosburgh,
Jesse Brandeburg, Jonathan Corbet, linux-doc, linux-kernel,
netdev, oss-drivers, Paolo Abeni, Raju Rangoju, Saeed Mahameed,
Simon Horman, Tony Nguyen, Veaceslav Falico
On Tue, 24 Jan 2023 13:54:56 +0200 Leon Romanovsky wrote:
> This series continues effort started by Sabrina to return XFRM configuration
> errors through extack. It allows for user space software stack easily present
> driver failure reasons to users.
Steffen, would you like to take these into your tree or should we apply
directly? Looks like mostly driver changes.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack
2023-01-25 19:01 ` Jakub Kicinski
@ 2023-01-26 9:43 ` Steffen Klassert
0 siblings, 0 replies; 4+ messages in thread
From: Steffen Klassert @ 2023-01-26 9:43 UTC (permalink / raw)
To: Jakub Kicinski
Cc: Leon Romanovsky, David S . Miller, Andy Gospodarek, Ayush Sawal,
Eric Dumazet, Herbert Xu, intel-wired-lan, Jay Vosburgh,
Jesse Brandeburg, Jonathan Corbet, linux-doc, linux-kernel,
netdev, oss-drivers, Paolo Abeni, Raju Rangoju, Saeed Mahameed,
Simon Horman, Tony Nguyen, Veaceslav Falico
On Wed, Jan 25, 2023 at 11:01:33AM -0800, Jakub Kicinski wrote:
> On Tue, 24 Jan 2023 13:54:56 +0200 Leon Romanovsky wrote:
> > This series continues effort started by Sabrina to return XFRM configuration
> > errors through extack. It allows for user space software stack easily present
> > driver failure reasons to users.
>
> Steffen, would you like to take these into your tree or should we apply
> directly? Looks like mostly driver changes.
You can just take it directly as it is mostly driver changes.
The ipsec-next tree is currently empty so there will be no
conflicts.
Thanks!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack
2023-01-24 11:54 [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack Leon Romanovsky
2023-01-25 19:01 ` Jakub Kicinski
@ 2023-01-27 0:50 ` patchwork-bot+netdevbpf
1 sibling, 0 replies; 4+ messages in thread
From: patchwork-bot+netdevbpf @ 2023-01-27 0:50 UTC (permalink / raw)
To: Leon Romanovsky
Cc: davem, kuba, steffen.klassert, andy, ayush.sawal, edumazet,
herbert, intel-wired-lan, j.vosburgh, jesse.brandeburg, corbet,
linux-doc, linux-kernel, netdev, oss-drivers, pabeni, rajur,
saeedm, simon.horman, anthony.l.nguyen, vfalico
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Jan 2023 13:54:56 +0200 you wrote:
> Changelog
> v1:
> * Fixed rebase errors in mlx5 and cxgb4 drivers
> * Fixed previously existed typo in nfp driver
> * Added Simon's ROB
> * Removed my double SOB tags
> v0: https://lore.kernel.org/all/cover.1674481435.git.leon@kernel.org
>
> [...]
Here is the summary with links:
- [net-next,v1,01/10] xfrm: extend add policy callback to set failure reason
https://git.kernel.org/netdev/net-next/c/3089386db090
- [net-next,v1,02/10] net/mlx5e: Fill IPsec policy validation failure reason
https://git.kernel.org/netdev/net-next/c/1bb70c5ab6ec
- [net-next,v1,03/10] xfrm: extend add state callback to set failure reason
https://git.kernel.org/netdev/net-next/c/7681a4f58fb9
- [net-next,v1,04/10] net/mlx5e: Fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/902812b81604
- [net-next,v1,05/10] netdevsim: Fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/6c4869795568
- [net-next,v1,06/10] nfp: fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/05ddf5f8cb6c
- [net-next,v1,07/10] ixgbevf: fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/c068ec5c964d
- [net-next,v1,08/10] ixgbe: fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/505c500cfcb4
- [net-next,v1,09/10] bonding: fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/3fe57986271a
- [net-next,v1,10/10] cxgb4: fill IPsec state validation failure reason
https://git.kernel.org/netdev/net-next/c/8c284ea429d2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-01-27 0:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-24 11:54 [PATCH net-next v1 00/10] Convert drivers to return XFRM configuration errors through extack Leon Romanovsky
2023-01-25 19:01 ` Jakub Kicinski
2023-01-26 9:43 ` Steffen Klassert
2023-01-27 0:50 ` patchwork-bot+netdevbpf
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).