From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, kernel test robot <lkp@intel.com>,
Christoph Hellwig <hch@lst.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: drivers/pci/p2pdma.c:199:44: sparse: sparse: dereference of noderef expression
Date: Mon, 6 Feb 2023 15:26:27 +0000 [thread overview]
Message-ID: <6359dcaa-0817-4819-321c-f786809ff89d@nvidia.com> (raw)
In-Reply-To: <202302020153.4eL3mwiK-lkp@intel.com>
Logan,
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> sparse warnings: (new ones prefixed by >>)
>>> drivers/pci/p2pdma.c:199:44: sparse: sparse: dereference of noderef expression
>
> vim +199 drivers/pci/p2pdma.c
>
> 193
> 194 static void p2pdma_page_free(struct page *page)
> 195 {
> 196 struct pci_p2pdma_pagemap *pgmap = to_p2p_pgmap(page->pgmap);
> 197 struct percpu_ref *ref;
> 198
> > 199 gen_pool_free_owner(pgmap->provider->p2pdma->pool,
> 200 (uintptr_t)page_to_virt(page), PAGE_SIZE,
> 201 (void **)&ref);
> 202 percpu_ref_put(ref);
> 203 }
> 204
>
Did you get a chance to look into this ?
-ck
next prev parent reply other threads:[~2023-02-06 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 17:31 kernel test robot
2023-02-06 15:26 ` Chaitanya Kulkarni [this message]
2023-02-06 18:21 ` Logan Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2022-12-27 21:01 kernel test robot
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=6359dcaa-0817-4819-321c-f786809ff89d@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=logang@deltatee.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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