From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>, <horms@kernel.org>,
"Aleksandr Loktionov" <aleksandr.loktionov@intel.com>
Cc: <alok.a.tiwarilinux@gmail.com>, <anthony.l.nguyen@intel.com>,
<andrew+netdev@lunn.ch>, <kuba@kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<aleksander.lobakin@intel.com>
Subject: Re: [PATCH net-next] iavf: fix incorrect warning message in iavf_del_vlans()
Date: Mon, 27 Oct 2025 09:45:18 +0100 [thread overview]
Message-ID: <47f8c95c-bac4-471f-8e58-9155c6e58cb5@intel.com> (raw)
In-Reply-To: <20251024134636.1464666-1-alok.a.tiwari@oracle.com>
On 10/24/25 15:46, Alok Tiwari wrote:
> The warning message refers to "add VLAN changes" instead of
> "delete VLAN changes". Update the log string to use the correct text.
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> ---
> drivers/net/ethernet/intel/iavf/iavf_virtchnl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c b/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> index 34a422a4a29c..6ad91db027d3 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> @@ -987,7 +987,7 @@ void iavf_del_vlans(struct iavf_adapter *adapter)
>
> len = virtchnl_struct_size(vvfl_v2, filters, count);
> if (len > IAVF_MAX_AQ_BUF_SIZE) {
> - dev_warn(&adapter->pdev->dev, "Too many add VLAN changes in one request\n");
> + dev_warn(&adapter->pdev->dev, "Too many delete VLAN changes in one request\n");
> while (len > IAVF_MAX_AQ_BUF_SIZE)
> len = virtchnl_struct_size(vvfl_v2, filters,
> --count);
As Simon said this is a clear copy-paste error.
But the message itself is not great:
there is too many VLAN DEL requests to fit into 4k of memory, so what?
driver will just split into multiple virtchnl messages (with the "loop"
for splitting is put multiple call layers above from iavf_del_vlans()),
and everything is expected to work fine (despite the fact that this is
likely not tested frequently ;))
I would suggest to also lover the log message level to info, and
rephrase as "Too many VLAN delete changes requested, splitting into
multiple messages to PF",
or similar. And the same for ADD requests, the same for v1 message
(so 4 cases total).
with that there will be no eyebrow raised for the dmesg reader
next prev parent reply other threads:[~2025-10-27 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 13:46 [PATCH net-next] iavf: fix incorrect warning message in iavf_del_vlans() Alok Tiwari
2025-10-24 17:13 ` Simon Horman
2025-10-27 7:18 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-27 8:45 ` Przemek Kitszel [this message]
2025-10-31 14:17 ` [External] : " ALOK TIWARI
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=47f8c95c-bac4-471f-8e58-9155c6e58cb5@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=alok.a.tiwarilinux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).