From: Jacob Keller <jacob.e.keller@intel.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 08/10] devlink: implement DEVLINK_CMD_REGION_NEW
Date: Wed, 25 Mar 2020 18:30:35 -0700 [thread overview]
Message-ID: <fe618551-3108-958a-ca6d-69c2b6fd43a6@intel.com> (raw)
In-Reply-To: <20200325164622.GZ11304@nanopsycho.orion>
On 3/25/2020 9:46 AM, Jiri Pirko wrote:
> Tue, Mar 24, 2020 at 11:34:43PM CET, jacob.e.keller@intel.com wrote:
>> +
>> + /* Check to make sure it's empty first */
>> + if (xa_load(&devlink->snapshot_ids, id))
>
> How this can happen? The entry was just allocated. WARN_ON.
>
Sure, I'll add WARN_ON. I think the return should still be kept, since
it causes the caller to fail instead of accidentally overwriting the
snapshot count.
>
>> + return -EBUSY;
>> +
>> + err = xa_err(xa_store(&devlink->snapshot_ids, id, xa_mk_value(0),
>> + GFP_KERNEL));
>
> Just return and avoid err variable.
>
Yep, done.
>> +
>> + if (region->cur_snapshots == region->max_snapshots) {
>> + NL_SET_ERR_MSG_MOD(info->extack, "The region has reached the maximum number of stored snapshots");
>> + return -ENOMEM;
>
> Maybe ENOBUFS or ENOSPC? ENOMEM seems odd as it is related to memory
> allocation fails which this is not.
>
Hmmm. This actually appears to be duplicated from the snapshot_create
function which used ENOMEM. Will add a patch to clean that up first.
It seems like we end up duplicating checks from within the
__devlink_region_snapshot_create merely because we have the extack
pointer here...
>
>> + }
>> +
>> + snapshot_id = nla_get_u32(info->attrs[DEVLINK_ATTR_REGION_SNAPSHOT_ID]);
>> +
>> + if (devlink_region_snapshot_get_by_id(region, snapshot_id)) {
>> + NL_SET_ERR_MSG_MOD(info->extack, "The requested snapshot id is already in use");
>> + return -EEXIST;
>> + }
>> +
>> + err = __devlink_snapshot_id_insert(devlink, snapshot_id);
>> + if (err) {
>> + NL_SET_ERR_MSG_MOD(info->extack, "The requested snapshot id is already in used");
>
> Different message would be appropriate.
>
Right. This is the "this shouldn't happen" case from above I think.
>
>> + return err;
>> + }
>> +
>> + err = region->ops->snapshot(devlink, info->extack, &data);
>> + if (err)
>> + goto err_decrement_snapshot_count;
>> +
>> + err = __devlink_region_snapshot_create(region, data, snapshot_id);
>> + if (err)
>> + goto err_free_snapshot_data;
>> +
>> + return 0;
>> +
>> +err_decrement_snapshot_count:
>> + __devlink_snapshot_id_decrement(devlink, snapshot_id);
>> +err_free_snapshot_data:
>
> In devlink the error labers are named according to actions that failed.
> Please align.
>
Sure.
Thanks,
Jake
next prev parent reply other threads:[~2020-03-26 1:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 22:34 [PATCH 00/10] implement DEVLINK_CMD_REGION_NEW Jacob Keller
2020-03-24 22:34 ` [PATCH 01/10] devlink: prepare to support region operations Jacob Keller
2020-03-24 22:34 ` [PATCH 02/10] devlink: convert snapshot destructor callback to region op Jacob Keller
2020-03-24 22:34 ` [PATCH 03/10] devlink: trivial: fix tab in function documentation Jacob Keller
2020-03-24 22:34 ` [PATCH 04/10] devlink: add function to take snapshot while locked Jacob Keller
2020-03-25 17:56 ` Jakub Kicinski
2020-03-24 22:34 ` [PATCH 05/10] devlink: extract snapshot id allocation to helper function Jacob Keller
2020-03-25 14:08 ` Jiri Pirko
2020-03-24 22:34 ` [PATCH 06/10] devlink: convert snapshot id getter to return an error Jacob Keller
2020-03-25 18:04 ` Jakub Kicinski
2020-03-25 19:13 ` Jiri Pirko
2020-03-26 1:33 ` Jacob Keller
2020-03-24 22:34 ` [PATCH] devlink: track snapshot id usage count using an xarray Jacob Keller
2020-03-25 16:08 ` Jiri Pirko
2020-03-26 1:16 ` Jacob Keller
2020-03-26 1:43 ` Jacob Keller
2020-03-24 22:34 ` [PATCH 08/10] devlink: implement DEVLINK_CMD_REGION_NEW Jacob Keller
2020-03-25 16:46 ` Jiri Pirko
2020-03-25 17:18 ` Jakub Kicinski
2020-03-25 17:20 ` Jiri Pirko
2020-03-25 17:46 ` Jakub Kicinski
2020-03-25 18:41 ` Jiri Pirko
2020-03-26 1:30 ` Jacob Keller [this message]
2020-03-24 22:34 ` [PATCH 09/10] netdevsim: support taking immediate snapshot via devlink Jacob Keller
2020-03-25 16:50 ` Jiri Pirko
2020-03-24 22:34 ` [PATCH 10/10] ice: add a devlink region for dumping NVM contents Jacob Keller
2020-03-25 17:18 ` Jiri Pirko
2020-03-25 13:49 ` [PATCH 00/10] implement DEVLINK_CMD_REGION_NEW Jiri Pirko
2020-03-25 13:50 ` Jiri Pirko
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=fe618551-3108-958a-ca6d-69c2b6fd43a6@intel.com \
--to=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).