From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: rasland@mellanox.com
Cc: dev@dpdk.org, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] net/failsafe: fix for missing pclose after popen
Date: Thu, 3 Aug 2017 15:58:31 +0200 [thread overview]
Message-ID: <20170803135831.GG8124@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1501765798-14200-1-git-send-email-rasland@mellanox.com>
Hi Raslan,
I sent a patch earlier regarding this but we will use yours.
Two small nits below.
On Thu, Aug 03, 2017 at 04:09:58PM +0300, rasland@mellanox.com wrote:
> From: Raslan Darawsheh <rasland@mellanox.com>
>
> When there is no prefered device, failsafe will always
> try to scan for prefered device. And if there is no device
> found with the exec option, popen() will get an empty output.
> In this case, it was forgotten to close the file descriptor.o
> it is fixed by closing the file descriptor even if the output is emtpy.
>
Good job on finding the issue and fixing it.
It has been assigned a coverity ID:
Coverity issue: 158633
> Fixes: a0194d82 ("net/failsafe: add flexible device definition")
>
The fixline should be 12-char long I think:
Fixes: a0194d828100 ("net/failsafe: add flexible device definition")
> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
Otherwise:
Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> ---
> drivers/net/failsafe/failsafe_args.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/failsafe/failsafe_args.c b/drivers/net/failsafe/failsafe_args.c
> index 932e371..3f92a77 100644
> --- a/drivers/net/failsafe/failsafe_args.c
> +++ b/drivers/net/failsafe/failsafe_args.c
> @@ -115,7 +115,7 @@ fs_execute_cmd(struct sub_device *sdev, char *cmdline)
> char output[DEVARGS_MAXLEN + 1];
> size_t len;
> int old_err;
> - int ret;
> + int ret, pclose_ret;
>
> RTE_ASSERT(cmdline != NULL || sdev->cmdline != NULL);
> if (sdev->cmdline == NULL) {
> @@ -145,7 +145,8 @@ fs_execute_cmd(struct sub_device *sdev, char *cmdline)
> /* We only read one line */
> if (fgets(output, sizeof(output) - 1, fp) == NULL) {
> DEBUG("Could not read command output");
> - return -ENODEV;
> + ret = -ENODEV;
> + goto ret_pclose;
> }
> fs_sanitize_cmdline(output);
> ret = fs_parse_device(sdev, output);
> @@ -154,12 +155,12 @@ fs_execute_cmd(struct sub_device *sdev, char *cmdline)
> goto ret_pclose;
> }
> ret_pclose:
> - ret = pclose(fp);
> - if (ret) {
> - ret = errno;
> + pclose_ret = pclose(fp);
> + if (pclose_ret) {
> + pclose_ret = errno;
> ERROR("pclose: %s", strerror(errno));
> errno = old_err;
> - return ret;
> + return pclose_ret;
> }
> return ret;
> }
> --
> 2.7.4
>
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2017-08-03 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 13:09 rasland
2017-08-03 13:58 ` Gaëtan Rivet [this message]
2017-08-03 20:32 ` Thomas Monjalon
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=20170803135831.GG8124@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
--cc=rasland@mellanox.com \
--cc=thomas@monjalon.net \
/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).