From: Jason Gunthorpe <jgg@nvidia.com>
To: coverity-bot <keescook@chromium.org>
Cc: Nicolin Chen <nicolinc@nvidia.com>, Yi Liu <yi.l.liu@intel.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: Coverity: iopt_map_user_pages(): Memory - illegal accesses
Date: Wed, 2 Nov 2022 17:07:26 -0300 [thread overview]
Message-ID: <Y2LN/j3Kcj09xwAJ@nvidia.com> (raw)
In-Reply-To: <202211021254.4B47DCD2@keescook>
On Wed, Nov 02, 2022 at 12:54:40PM -0700, coverity-bot wrote:
> *** CID 1527094: Memory - illegal accesses (UNINIT)
> /drivers/iommu/iommufd/io_pagetable.c: 415 in iopt_map_user_pages()
> 409 elm.start_byte = uptr - elm.pages->uptr;
> 410 elm.length = length;
> 411 list_add(&elm.next, &pages_list);
> 412
> 413 rc = iopt_map_pages(iopt, &pages_list, length, iova, iommu_prot, flags);
> 414 if (rc) {
> vvv CID 1527094: Memory - illegal accesses (UNINIT)
> vvv Using uninitialized value "elm.area".
> 415 if (elm.area)
> 416 iopt_abort_area(elm.area);
> 417 if (elm.pages)
> 418 iopt_put_pages(elm.pages);
> 419 return rc;
> 420 }
>
> If this is a false positive, please let us know so we can mark it as
> such, or teach the Coverity rules to be smarter. If not, please make
> sure fixes get into linux-next. :) For patches fixing this, please
> include these lines (but double-check the "Fixes" first):
Yep, I will squash this in:
- struct iopt_pages_list elm;
+ struct iopt_pages_list elm = {};
LIST_HEAD(pages_list);
int rc;
Thanks,
Jason
prev parent reply other threads:[~2022-11-02 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 19:54 Coverity: iopt_map_user_pages(): Memory - illegal accesses coverity-bot
2022-11-02 20:07 ` Jason Gunthorpe [this message]
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=Y2LN/j3Kcj09xwAJ@nvidia.com \
--to=jgg@nvidia.com \
--cc=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=yi.l.liu@intel.com \
/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.