From: Jonathan Cameron <jic23@kernel.org>
To: Petre Rodan <petre.rodan@subdimension.ro>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 1/1] tools: iio: fix iio_generic_buffer
Date: Sun, 7 Jan 2024 15:53:33 +0000 [thread overview]
Message-ID: <20240107155333.0e43b041@jic23-huawei> (raw)
In-Reply-To: <20240104101253.25896-2-petre.rodan@subdimension.ro>
On Thu, 4 Jan 2024 12:12:45 +0200
Petre Rodan <petre.rodan@subdimension.ro> wrote:
> Fix code flow problem and floating point exception caused by improper
> directory stream positioning.
>
> Fixes: <e58537ccce733> ("staging: iio: update example application.")
> Signed-off-by: Petre Rodan <petre.rodan@subdimension.ro>
Hi Petre,
This doesn't really explain 'why' seeekdir(dp, 0) is wrong.
My assumption is that telldir() would not have returned 0 on this particular
system? Could you confirm that and update the message to explain why
seekdir(dp, 0) is not equivalent to rewinddir(dp).
Thanks,
Jonathan
> ---
> tools/iio/iio_utils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/iio/iio_utils.c b/tools/iio/iio_utils.c
> index 6a00a6eecaef..c5c5082cb24e 100644
> --- a/tools/iio/iio_utils.c
> +++ b/tools/iio/iio_utils.c
> @@ -376,7 +376,7 @@ int build_channel_array(const char *device_dir, int buffer_idx,
> goto error_close_dir;
> }
>
> - seekdir(dp, 0);
> + rewinddir(dp);
> while (ent = readdir(dp), ent) {
> if (strcmp(ent->d_name + strlen(ent->d_name) - strlen("_en"),
> "_en") == 0) {
> --
> 2.41.0
>
next prev parent reply other threads:[~2024-01-07 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 10:12 [PATCH 0/1] tools: iio: fix iio_generic_buffer Petre Rodan
2024-01-04 10:12 ` [PATCH 1/1] " Petre Rodan
2024-01-07 15:53 ` Jonathan Cameron [this message]
2024-01-07 16:28 ` Petre Rodan
2024-01-07 17:00 ` Jonathan Cameron
2024-01-07 17:04 ` Petre Rodan
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=20240107155333.0e43b041@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petre.rodan@subdimension.ro \
/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