From: Alex Williamson <alex.williamson@redhat.com>
To: Cong Liu <liucong2@kylinos.cn>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix build error in function vfio_combine_iova_ranges
Date: Mon, 11 Sep 2023 12:44:31 -0600 [thread overview]
Message-ID: <20230911124431.5e09f53b.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230911094103.57771-1-liucong2@kylinos.cn>
On Mon, 11 Sep 2023 17:41:02 +0800
Cong Liu <liucong2@kylinos.cn> wrote:
> when compiling with smatch check, the following errors were encountered:
>
> drivers/vfio/vfio_main.c:957 vfio_combine_iova_ranges() error: uninitialized symbol 'last'.
> drivers/vfio/vfio_main.c:978 vfio_combine_iova_ranges() error: potentially dereferencing uninitialized 'comb_end'.
> drivers/vfio/vfio_main.c:978 vfio_combine_iova_ranges() error: potentially dereferencing uninitialized 'comb_start'.
>
> this patch fix these error.
>
> Signed-off-by: Cong Liu <liucong2@kylinos.cn>
> ---
> drivers/vfio/vfio_main.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
> index 40732e8ed4c6..0a9620409696 100644
> --- a/drivers/vfio/vfio_main.c
> +++ b/drivers/vfio/vfio_main.c
> @@ -938,12 +938,13 @@ static int vfio_ioctl_device_feature_migration(struct vfio_device *device,
> void vfio_combine_iova_ranges(struct rb_root_cached *root, u32 cur_nodes,
> u32 req_nodes)
> {
> - struct interval_tree_node *prev, *curr, *comb_start, *comb_end;
> + struct interval_tree_node *prev, *curr;
> + struct interval_tree_node *comb_start, *comb_end;
This looks cosmetic, what did it fix? It's not clear to me how any of
this addresses the last two errors. Thanks,
Alex
> unsigned long min_gap, curr_gap;
>
> /* Special shortcut when a single range is required */
> if (req_nodes == 1) {
> - unsigned long last;
> + unsigned long last = 0;
>
> comb_start = interval_tree_iter_first(root, 0, ULONG_MAX);
> curr = comb_start;
next prev parent reply other threads:[~2023-09-11 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 9:41 Cong Liu
2023-09-11 18:44 ` Alex Williamson [this message]
2023-09-12 1:07 ` Cong Liu
2023-09-13 12:36 ` Jason Gunthorpe
2023-09-14 9:08 ` [PATCH v2] vfio: Fix uninitialized symbol and potential dereferencing errors in vfio_combine_iova_ranges Cong Liu
2023-09-19 18:04 ` Alex Williamson
2023-09-20 9:55 ` [PATCH v3] " Cong Liu
2023-10-02 22:41 ` Alex Williamson
2023-10-02 22:43 ` [PATCH] vfio: Fix smatch errors in vfio_combine_iova_ranges() Alex Williamson
2023-10-04 15:35 ` Brett Creeley
2023-10-06 16:56 ` Jason Gunthorpe
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=20230911124431.5e09f53b.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liucong2@kylinos.cn \
/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
Powered by JetHome