From: Jiri Pirko <jiri@resnulli.us>
To: "Lucero Palau, Alejandro" <alejandro.lucero-palau@amd.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-net-drivers (AMD-Xilinx)" <linux-net-drivers@amd.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"habetsm.xilinx@gmail.com" <habetsm.xilinx@gmail.com>,
"ecree.xilinx@gmail.com" <ecree.xilinx@gmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"jiri@nvidia.com" <jiri@nvidia.com>
Subject: Re: [PATCH v5 net-next 2/8] sfc: add devlink info support for ef100
Date: Wed, 8 Feb 2023 08:35:58 +0100 [thread overview]
Message-ID: <Y+NQ3tuK6hnDmvah@nanopsycho> (raw)
In-Reply-To: <DM6PR12MB4202E78CB7CB3BE13817B782C1DB9@DM6PR12MB4202.namprd12.prod.outlook.com>
Tue, Feb 07, 2023 at 06:24:05PM CET, alejandro.lucero-palau@amd.com wrote:
>
>On 2/7/23 15:10, Lucero Palau, Alejandro wrote:
>> On 2/7/23 14:58, Jiri Pirko wrote:
>>> Tue, Feb 07, 2023 at 03:42:45PM CET, alejandro.lucero-palau@amd.com wrote:
>>>> On 2/2/23 11:58, Jiri Pirko wrote:
>>>>> Thu, Feb 02, 2023 at 12:14:17PM CET, alejandro.lucero-palau@amd.com wrote:
>>>>>> From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
>>>>>>
>>>>>> Support for devlink info command.
>>>>> You are quite brief for couple hundred line patch. Care to shed some
>>>>> more details for the reader? Also, use imperative mood (applies to the
>>>>> rest of the pathes)
>>>>>
>>>>> [...]
>>>>>
>>>> OK. I'll be more talkative and imperative here.
>>>>
>>>>>> +static int efx_devlink_info_get(struct devlink *devlink,
>>>>>> + struct devlink_info_req *req,
>>>>>> + struct netlink_ext_ack *extack)
>>>>>> +{
>>>>>> + struct efx_devlink *devlink_private = devlink_priv(devlink);
>>>>>> + struct efx_nic *efx = devlink_private->efx;
>>>>>> + char msg[NETLINK_MAX_FMTMSG_LEN];
>>>>>> + int errors_reported = 0;
>>>>>> + int rc;
>>>>>> +
>>>>>> + /* Several different MCDI commands are used. We report first error
>>>>>> + * through extack along with total number of errors. Specific error
>>>>>> + * information via system messages.
>>>>>> + */
>>>>>> + rc = efx_devlink_info_board_cfg(efx, req);
>>>>>> + if (rc) {
>>>>>> + sprintf(msg, "Getting board info failed");
>>>>>> + errors_reported++;
>>>>>> + }
>>>>>> + rc = efx_devlink_info_stored_versions(efx, req);
>>>>>> + if (rc) {
>>>>>> + if (!errors_reported)
>>>>>> + sprintf(msg, "Getting stored versions failed");
>>>>>> + errors_reported += rc;
>>>>>> + }
>>>>>> + rc = efx_devlink_info_running_versions(efx, req);
>>>>>> + if (rc) {
>>>>>> + if (!errors_reported)
>>>>>> + sprintf(msg, "Getting board info failed");
>>>>>> + errors_reported++;
>>>>> Under which circumstances any of the errors above happen? Is it a common
>>>>> thing? Or is it result of some fatal event?
>>>> They are not common at all. If any of those happen, it is a bad sign,
>>>> and it is more than likely there are more than one because something is
>>>> not working properly. That is the reason I only report first error found
>>>> plus the total number of errors detected.
>>>>
>>>>
>>>>> You treat it like it is quite common, which seems very odd to me.
>>>>> If they are rare, just return error right away to the caller.
>>>> Well, that is done now. And as I say, I'm not reporting all but just the
>>>> first one, mainly because the buffer limitation with NETLINK_MAX_FMTMSG_LEN.
>>>>
>>>> If errors trigger, a more complete information will appear in system
>>>> messages, so that is the reason with:
>>>>
>>>> + NL_SET_ERR_MSG_FMT(extack,
>>>> + "%s. %d total errors. Check system messages",
>>>> + msg, errors_reported);
>>>>
>>>> I guess you are concerned with the extack report being overwhelmed, but
>>>> I do not think that is the case.
>>> No, I'm wondering why you just don't put error message into exack and
>>> return -ESOMEERROR right away.
>> Well, I thought the idea was to give more information to user space
>> about the problem.
>>
>> Previous patchsets were not reporting any error nor error information
>> through extack. Now we have both.
>
>
>Just trying to make more sense of this.
>
>Because that limit with NETLINK_MAX_FMTMSG_LEN, what I think is big
>enough, some control needs to be taken about what to report. It could be
>just to write the buffer with the last error and report that last one
Wait. My point is: fail on the first error returning the error to
info_get() caller. Just that. No accumulation of anything.
>only, with no need of keeping total errors count. But I felt once we
>handle any error, reporting that extra info about the total errors
>detected should not be a problem at all, even if it is an unlikely
>situation.
>
>BTW, I said we were reporting both, the error and the extack error
>message, but I've realized the function was not returning any error but
>always 0, so I'll fix that.
>
>
>>>>>> + }
>>>>>> +
>>>>>> + if (errors_reported)
>>>>>> + NL_SET_ERR_MSG_FMT(extack,
>>>>>> + "%s. %d total errors. Check system messages",
>>>>>> + msg, errors_reported);
>>>>>> + return 0;
>>>>>> +}
>>>>>> +
>>>>>> static const struct devlink_ops sfc_devlink_ops = {
>>>>>> + .info_get = efx_devlink_info_get,
>>>>>> };
>>>>> [...]
next prev parent reply other threads:[~2023-02-08 7:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 11:14 [PATCH v5 net-next 0/8] sfc: devlink support for ef100 alejandro.lucero-palau
2023-02-02 11:14 ` [PATCH v5 net-next 1/8] sfc: add " alejandro.lucero-palau
2023-02-02 11:50 ` Jiri Pirko
2023-02-06 12:00 ` Edward Cree
2023-02-07 14:21 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 2/8] sfc: add devlink info " alejandro.lucero-palau
2023-02-02 11:58 ` Jiri Pirko
2023-02-07 14:42 ` Lucero Palau, Alejandro
2023-02-07 14:58 ` Jiri Pirko
2023-02-07 15:10 ` Lucero Palau, Alejandro
2023-02-07 17:24 ` Lucero Palau, Alejandro
2023-02-08 7:35 ` Jiri Pirko [this message]
2023-02-08 8:53 ` Lucero Palau, Alejandro
2023-02-03 2:37 ` kernel test robot
2023-02-03 11:38 ` kernel test robot
2023-02-02 11:14 ` [PATCH v5 net-next 3/8] sfc: enumerate mports in ef100 alejandro.lucero-palau
2023-02-06 12:38 ` Edward Cree
2023-02-07 15:14 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 4/8] sfc: add mport lookup based on driver's mport data alejandro.lucero-palau
2023-02-02 11:14 ` [PATCH v5 net-next 5/8] sfc: add devlink port support for ef100 alejandro.lucero-palau
2023-02-02 12:01 ` Jiri Pirko
2023-02-06 14:02 ` Edward Cree
2023-02-07 15:20 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 6/8] sfc: obtain device mac address based on firmware handle " alejandro.lucero-palau
2023-02-02 11:14 ` [PATCH v5 net-next 7/8] sfc: add support for devlink port_function_hw_addr_get in ef100 alejandro.lucero-palau
2023-02-02 12:09 ` Jiri Pirko
2023-02-07 15:01 ` Lucero Palau, Alejandro
2023-02-08 8:50 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 8/8] sfc: add support for devlink port_function_hw_addr_set " alejandro.lucero-palau
2023-02-02 12:13 ` Jiri Pirko
2023-02-07 15:06 ` Lucero Palau, Alejandro
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=Y+NQ3tuK6hnDmvah@nanopsycho \
--to=jiri@resnulli.us \
--cc=alejandro.lucero-palau@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--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).