From: Alistair Popple <apopple@nvidia.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-mm@kvack.org
Subject: Re: [bug report] mm/gup: migrate device coherent pages when pinning instead of failing
Date: Tue, 19 Jul 2022 22:04:57 +1000 [thread overview]
Message-ID: <8735excner.fsf@nvdebian.thelocal> (raw)
In-Reply-To: <YtZ8Z5os9Lh9NiLm@kili>
Dan Carpenter <dan.carpenter@oracle.com> writes:
> Hello Alistair Popple,
>
> The patch b05a79d4377f: "mm/gup: migrate device coherent pages when
> pinning instead of failing" from Jul 15, 2022, leads to the following
> Smatch static checker warning:
>
> mm/migrate_device.c:842 migrate_device_coherent_page()
> warn: duplicate check 'src_pfn & (1 << 1)' (previous on line 832)
>
> mm/migrate_device.c
> 810 int migrate_device_coherent_page(struct page *page)
> 811 {
> 812 unsigned long src_pfn, dst_pfn = 0;
> 813 struct migrate_vma args;
> 814 struct page *dpage;
> 815
> 816 WARN_ON_ONCE(PageCompound(page));
> 817
> 818 lock_page(page);
> 819 src_pfn = migrate_pfn(page_to_pfn(page)) | MIGRATE_PFN_MIGRATE;
> 820 args.src = &src_pfn;
> 821 args.dst = &dst_pfn;
> 822 args.cpages = 1;
> 823 args.npages = 1;
> 824 args.vma = NULL;
> 825
> 826 /*
> 827 * We don't have a VMA and don't need to walk the page tables to find
> 828 * the source page. So call migrate_vma_unmap() directly to unmap the
> 829 * page as migrate_vma_setup() will fail if args.vma == NULL.
> 830 */
> 831 migrate_vma_unmap(&args);
> 832 if (!(src_pfn & MIGRATE_PFN_MIGRATE))
> 833 return -EBUSY;
>
> Return here.
>
> 834
> 835 dpage = alloc_page(GFP_USER | __GFP_NOWARN);
> 836 if (dpage) {
> 837 lock_page(dpage);
> 838 dst_pfn = migrate_pfn(page_to_pfn(dpage));
> 839 }
> 840
> 841 migrate_vma_pages(&args);
> --> 842 if (src_pfn & MIGRATE_PFN_MIGRATE)
> 843 copy_highpage(dpage, page);
>
> No need to check again. Was dst_pfn intended?
No. The check is necessary and correct. migrate_vma_pages() may clear
MIGRATE_PFN_MIGRATE from src_pfn if the page could not be migrated for
some reason.
> 844 migrate_vma_finalize(&args);
> 845
> 846 if (src_pfn & MIGRATE_PFN_MIGRATE)
> 847 return 0;
>
> Same check again.
I don't see the problem with this?
- Alistair
> 848 return -EBUSY;
> 849 }
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2022-07-19 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 9:41 Dan Carpenter
2022-07-19 12:04 ` Alistair Popple [this message]
2022-07-19 13:00 ` Dan Carpenter
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=8735excner.fsf@nvdebian.thelocal \
--to=apopple@nvidia.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-mm@kvack.org \
/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