netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Vosburgh <jv@jvosburgh.net>
To: Jianbo Liu <jianbol@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, andy@greyhouse.net,
	saeedm@nvidia.com, gal@nvidia.com, leonro@nvidia.com,
	liuhangbin@gmail.com, tariqt@nvidia.com
Subject: Re: [PATCH net V6 0/3] Fixes for IPsec over bonding
Date: Fri, 23 Aug 2024 13:33:20 -0700	[thread overview]
Message-ID: <194957.1724445200@famine> (raw)
In-Reply-To: <20240823031056.110999-1-jianbol@nvidia.com>

Jianbo Liu <jianbol@nvidia.com> wrote:

>Hi,
>
>This patchset provides bug fixes for IPsec over bonding driver.
>
>It adds the missing xdo_dev_state_free API, and fixes "scheduling while
>atomic" by using mutex lock instead.
>
>Series generated against:
>commit c07ff8592d57 ("netem: fix return value if duplicate enqueue fails")
>
>Thanks!
>Jianbo

	I am not sufficiently familiar with the innards of IPsec to
comment on whether or not those aspects are correct, but the the other
changes look good to me.

	For the series:

Acked-by: Jay Vosburgh <jv@jvosburgh.net>

	-J

>V6
>- Add netdev_hold/netdev_put to prevent real_dev from being freed for
>  bond_ipsec_add_sa, bond_ipsec_del_sa and bond_ipsec_free_sa.
>
>V5:
>- Rebased.
>- Removed state deletion/free in bond_ipsec_add_sa_all() added before,
>  as real_dev is not set to NULL in Nikolay's patch. 
>
>V4:
>- Add to all patches: Reviewed-by: Hangbin Liu <liuhangbin@gmail.com>.
>- Update commit message in patch 1 (Jakub).
>
>V3:
>- Add RCU read lock/unlock for bond_ipsec_add_sa, bond_ipsec_del_sa and bond_ipsec_free_sa.
>
>V2:
>- Rebased on top of latest net branch.
>- Squashed patch #2 into #1 per Hangbin comment.
>- Addressed Hangbin's comments.
>- Patch #3 (was #4): Addressed comments by Paolo.
>
>Jianbo Liu (3):
>  bonding: implement xdo_dev_state_free and call it after deletion
>  bonding: extract the use of real_device into local variable
>  bonding: change ipsec_lock from spin lock to mutex
>
> drivers/net/bonding/bond_main.c | 159 +++++++++++++++++++++-----------
> include/net/bonding.h           |   2 +-
> 2 files changed, 106 insertions(+), 55 deletions(-)
>
>-- 
>2.21.0
>

---
	-Jay Vosburgh, jv@jvosburgh.net

  parent reply	other threads:[~2024-08-23 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23  3:10 [PATCH net V6 0/3] Fixes for IPsec over bonding Jianbo Liu
2024-08-23  3:10 ` [PATCH net V6 1/3] bonding: implement xdo_dev_state_free and call it after deletion Jianbo Liu
2024-08-23  3:10 ` [PATCH net V6 2/3] bonding: extract the use of real_device into local variable Jianbo Liu
2024-08-23  3:10 ` [PATCH net V6 3/3] bonding: change ipsec_lock from spin lock to mutex Jianbo Liu
2024-08-23 20:33 ` Jay Vosburgh [this message]
2024-08-27 20:20 ` [PATCH net V6 0/3] Fixes for IPsec over bonding patchwork-bot+netdevbpf

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=194957.1724445200@famine \
    --to=jv@jvosburgh.net \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jianbol@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).