From: Jiang, Dave <dave.jiang at intel.com>
To: accel-config@lists.01.org
Subject: [Accel-config] Re: [PATCH v1] accel-config: Fix static code analysis issues
Date: Fri, 04 Dec 2020 15:57:59 +0000 [thread overview]
Message-ID: <db7ed9e9fd344d08a8f32664e65dc137@intel.com> (raw)
In-Reply-To: 20201204111042.309062-1-ramesh.thomas@intel.com
[-- Attachment #1: Type: text/plain, Size: 3207 bytes --]
> -----Original Message-----
> From: ramesh.thomas(a)intel.com <ramesh.thomas(a)intel.com>
> Sent: Friday, December 4, 2020 4:11 AM
> To: accel-config(a)lists.01.org
> Cc: Luck, Tony <tony.luck(a)intel.com>; Jiang, Dave <dave.jiang(a)intel.com>;
> Thomas, Ramesh <ramesh.thomas(a)intel.com>
> Subject: [PATCH v1] accel-config: Fix static code analysis issues
>
> From: Ramesh Thomas <ramesh.thomas(a)intel.com>
>
> Fixed bugs found in static code analysis
For future bisect history, can you paste in the static code analysis complaint and explain what was fixed? Thanks!
>
> Signed-off-by: Ramesh Thomas <ramesh.thomas(a)intel.com>
> ---
> accfg/lib/libaccfg.c | 10 ++++++----
> accfg/list.c | 3 +--
> 2 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/accfg/lib/libaccfg.c b/accfg/lib/libaccfg.c index cd9da42..3b53be3
> 100644
> --- a/accfg/lib/libaccfg.c
> +++ b/accfg/lib/libaccfg.c
> @@ -529,7 +529,7 @@ static void *add_wq(void *parent, int id, const char
> *wq_base, {
> struct accfg_wq *wq;
> struct accfg_device *device = parent;
> - struct accfg_group *group = device->group;
> + struct accfg_group *group;
> struct accfg_ctx *ctx;
> char *path;
> char *wq_base_string;
> @@ -540,6 +540,7 @@ static void *add_wq(void *parent, int id, const char
> *wq_base,
> if (!device)
> return NULL;
>
> + group = device->group;
> ctx = accfg_device_get_ctx(device);
> dfd = open(wq_base, O_PATH);
> if (dfd < 0)
> @@ -615,7 +616,6 @@ err_read:
> free(wq->wq_buf);
> free(wq->wq_path);
> err_wq:
> - close(dfd);
> free(wq);
> free(path);
> return NULL;
> @@ -715,7 +715,7 @@ static void *add_engine(void *parent, int id, const
> char *engine_base,
> struct accfg_engine *engine;
> struct accfg_device *device = parent;
> struct accfg_ctx *ctx;
> - struct accfg_group *group = device->group;
> + struct accfg_group *group;
> char *path;
> char *engine_base_string;
> int dfd;
> @@ -724,6 +724,7 @@ static void *add_engine(void *parent, int id, const
> char *engine_base,
> if (!device)
> return NULL;
>
> + group = device->group;
> ctx = accfg_device_get_ctx(device);
> dfd = open(engine_base, O_PATH);
> if (dfd < 0)
> @@ -1109,12 +1110,13 @@ ACCFG_EXPORT int
> accfg_device_get_clients(struct accfg_device *device) ACCFG_EXPORT int
> accfg_device_set_token_limit(struct accfg_device *dev, int val) {
> struct accfg_ctx *ctx;
> - char *path = dev->device_buf;
> + char *path;
> char buf[SYSFS_ATTR_SIZE];
>
> if (!dev)
> return -EINVAL;
>
> + path = dev->device_buf;
> ctx = accfg_device_get_ctx(dev);
>
> if (sprintf(path, "%s/token_limit", dev->device_path) >= diff --git
> a/accfg/list.c b/accfg/list.c index c22da41..2234e65 100644
> --- a/accfg/list.c
> +++ b/accfg/list.c
> @@ -56,8 +56,7 @@ static struct json_object *group_to_json(struct
> accfg_group *group,
> struct json_object *jobj = NULL;
> struct accfg_device *dev = NULL;
>
> - if (group)
> - dev = accfg_group_get_device(group);
> + dev = accfg_group_get_device(group);
>
> if (!jgroup)
> return NULL;
> --
> 2.26.2
next reply other threads:[~2020-12-04 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 15:57 Jiang, Dave [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-04 16:23 [Accel-config] Re: [PATCH v1] accel-config: Fix static code analysis issues Luck, Tony
2020-12-04 18:42 Thomas, Ramesh
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=db7ed9e9fd344d08a8f32664e65dc137@intel.com \
--to=accel-config@lists.01.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 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.