From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Paolo Abeni <pabeni@redhat.com>,
Ayush Sawal <ayush.sawal@chelsio.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Eric Dumazet <edumazet@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Saeed Mahameed <saeedm@nvidia.com>,
oss-drivers@corigine.com, Veaceslav Falico <vfalico@gmail.com>,
Raju Rangoju <rajur@chelsio.com>,
Simon Horman <simon.horman@corigine.com>,
Jakub Kicinski <kuba@kernel.org>,
intel-wired-lan@lists.osuosl.org,
Leon Romanovsky <leonro@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Andy Gospodarek <andy@greyhouse.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next 09/10] bonding: fill IPsec state validation failure reason
Date: Mon, 23 Jan 2023 15:01:32 -0800 [thread overview]
Message-ID: <5064.1674514892@famine> (raw)
In-Reply-To: <d563de401d6fdc1c52959300eebb2bbb27c6c181.1674481435.git.leon@kernel.org>
Leon Romanovsky <leon@kernel.org> wrote:
>From: Leon Romanovsky <leonro@nvidia.com>
>
>Rely on extack to return failure reason.
>
>Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
>Signed-off-by: Leon Romanovsky <leon@kernel.org>
>---
> drivers/net/bonding/bond_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
>index 686b2a6fd674..00646aa315c3 100644
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -444,7 +444,7 @@ static int bond_ipsec_add_sa(struct xfrm_state *xs,
> if (!slave->dev->xfrmdev_ops ||
> !slave->dev->xfrmdev_ops->xdo_dev_state_add ||
> netif_is_bond_master(slave->dev)) {
>- slave_warn(bond_dev, slave->dev, "Slave does not support ipsec offload\n");
>+ NL_SET_ERR_MSG_MOD(extack, "Slave does not support ipsec offload");
> rcu_read_unlock();
> return -EINVAL;
> }
Why only this one, and not include the other similar
slave_warn() calls in the bond_ipsec_* functions? That would seem to
make some failures show up in dmesg, and others returned to the caller
via extack.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Steffen Klassert <steffen.klassert@secunet.com>,
Veaceslav Falico <vfalico@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jonathan Corbet <corbet@lwn.net>,
oss-drivers@corigine.com, linux-doc@vger.kernel.org,
Raju Rangoju <rajur@chelsio.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
Ayush Sawal <ayush.sawal@chelsio.com>,
Simon Horman <simon.horman@corigine.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Andy Gospodarek <andy@greyhouse.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next 09/10] bonding: fill IPsec state validation failure reason
Date: Mon, 23 Jan 2023 15:01:32 -0800 [thread overview]
Message-ID: <5064.1674514892@famine> (raw)
In-Reply-To: <d563de401d6fdc1c52959300eebb2bbb27c6c181.1674481435.git.leon@kernel.org>
Leon Romanovsky <leon@kernel.org> wrote:
>From: Leon Romanovsky <leonro@nvidia.com>
>
>Rely on extack to return failure reason.
>
>Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
>Signed-off-by: Leon Romanovsky <leon@kernel.org>
>---
> drivers/net/bonding/bond_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
>index 686b2a6fd674..00646aa315c3 100644
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -444,7 +444,7 @@ static int bond_ipsec_add_sa(struct xfrm_state *xs,
> if (!slave->dev->xfrmdev_ops ||
> !slave->dev->xfrmdev_ops->xdo_dev_state_add ||
> netif_is_bond_master(slave->dev)) {
>- slave_warn(bond_dev, slave->dev, "Slave does not support ipsec offload\n");
>+ NL_SET_ERR_MSG_MOD(extack, "Slave does not support ipsec offload");
> rcu_read_unlock();
> return -EINVAL;
> }
Why only this one, and not include the other similar
slave_warn() calls in the bond_ipsec_* functions? That would seem to
make some failures show up in dmesg, and others returned to the caller
via extack.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2023-01-23 23:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 14:00 [Intel-wired-lan] [PATCH net-next 00/10] Convert drivers to return XFRM configuration errors through extack Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 01/10] xfrm: extend add policy callback to set failure reason Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 02/10] net/mlx5e: Fill IPsec policy validation " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 03/10] xfrm: extend add state callback to set " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 04/10] net/mlx5e: Fill IPsec state validation " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 17:12 ` [Intel-wired-lan] " Leon Romanovsky
2023-01-23 17:12 ` Leon Romanovsky
2023-01-24 7:59 ` [Intel-wired-lan] " kernel test robot
2023-01-24 7:59 ` kernel test robot
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 05/10] netdevsim: " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 06/10] nfp: fill " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 15:09 ` [Intel-wired-lan] " Simon Horman
2023-01-23 15:09 ` Simon Horman
2023-01-23 16:34 ` [Intel-wired-lan] " Leon Romanovsky
2023-01-23 16:34 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 07/10] ixgbevf: " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 08/10] ixgbe: " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 09/10] bonding: " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-23 23:01 ` Jay Vosburgh [this message]
2023-01-23 23:01 ` [Intel-wired-lan] " Jay Vosburgh
2023-01-24 6:22 ` Leon Romanovsky
2023-01-24 6:22 ` Leon Romanovsky
2023-01-23 14:00 ` [Intel-wired-lan] [PATCH net-next 10/10] cxgb4: " Leon Romanovsky
2023-01-23 14:00 ` Leon Romanovsky
2023-01-24 9:42 ` [Intel-wired-lan] " kernel test robot
2023-01-24 9:42 ` kernel test robot
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=5064.1674514892@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=anthony.l.nguyen@intel.com \
--cc=ayush.sawal@chelsio.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=rajur@chelsio.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=steffen.klassert@secunet.com \
--cc=vfalico@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.