From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kas:kvm-unmapped-poison 7/7] mm/migrate.c:243 remove_migration_pte() warn: inconsistent indenting
Date: Sat, 13 Mar 2021 12:42:44 +0800 [thread overview]
Message-ID: <202103131242.kRmKEN2r-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git kvm-unmapped-poison
head: 51d4d402256b9c1b8e38be95bfa2bb28dc8189ad
commit: 51d4d402256b9c1b8e38be95bfa2bb28dc8189ad [7/7] KVM: unmap guest memory with poison
config: x86_64-randconfig-m001-20210312 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
smatch warnings:
mm/migrate.c:243 remove_migration_pte() warn: inconsistent indenting
vim +243 mm/migrate.c
230
231 get_page(new);
232 pte = pte_mkold(mk_pte(new, READ_ONCE(vma->vm_page_prot)));
233 if (pte_swp_soft_dirty(*pvmw.pte))
234 pte = pte_mksoft_dirty(pte);
235
236 /*
237 * Recheck VMA as permissions can change since migration started
238 */
239 entry = pte_to_swp_entry(*pvmw.pte);
240 if (is_hwpoison_entry(entry) && !PageHWPoison(page)) {
241 /* Unpoison the page */
242 pte = mk_pte(page, vma->vm_page_prot);
> 243 } if (is_write_migration_entry(entry))
244 pte = maybe_mkwrite(pte, vma);
245 else if (pte_swp_uffd_wp(*pvmw.pte))
246 pte = pte_mkuffd_wp(pte);
247
248 if (unlikely(is_device_private_page(new))) {
249 entry = make_device_private_entry(new, pte_write(pte));
250 pte = swp_entry_to_pte(entry);
251 if (pte_swp_soft_dirty(*pvmw.pte))
252 pte = pte_swp_mksoft_dirty(pte);
253 if (pte_swp_uffd_wp(*pvmw.pte))
254 pte = pte_swp_mkuffd_wp(pte);
255 }
256
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31553 bytes --]
reply other threads:[~2021-03-13 4:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202103131242.kRmKEN2r-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.