[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZVxdv9tkZ/QE5bUZ@nanopsycho>
Date: Tue, 21 Nov 2023 08:35:27 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, pabeni@...hat.com, davem@...emloft.net,
edumazet@...gle.com, jacob.e.keller@...el.com, jhs@...atatu.com,
johannes@...solutions.net, andriy.shevchenko@...ux.intel.com,
amritha.nambiar@...el.com, sdf@...gle.com, horms@...nel.org
Subject: Re: [patch net-next v3 8/9] devlink: add a command to set
notification filter and use it for multicasts
Tue, Nov 21, 2023 at 03:51:23AM CET, kuba@...nel.org wrote:
>On Mon, 20 Nov 2023 09:46:56 +0100 Jiri Pirko wrote:
>> + if (attrs[DEVLINK_ATTR_BUS_NAME])
>> + data_size += nla_len(attrs[DEVLINK_ATTR_BUS_NAME]) + 1;
>> + if (attrs[DEVLINK_ATTR_DEV_NAME])
>> + data_size += nla_len(attrs[DEVLINK_ATTR_DEV_NAME]) + 1;
>
>> + /* Don't attach empty filter. */
>> + if (!flt->bus_name && !flt->dev_name) {
>
>Should the attrs be checked with GENL_REQ_ATTR_CHECK() then?
No, they are all optional. This is for the case the user passes empty
message, that clears the filter.
Powered by blists - more mailing lists