All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, linux-hyperv@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Nuno Das Neves <nunodasneves@linux.microsoft.com>,
	Tianyu Lan <tiala@microsoft.com>,
	Michael Kelley <mhklinux@outlook.com>,
	Li Tian <litian@redhat.com>, Philipp Rudo <prudo@redhat.com>
Subject: Re: [PATCH v2] x86/hyperv: Fix kdump on Azure CVMs
Date: Wed, 20 Aug 2025 05:19:59 +0800	[thread overview]
Message-ID: <202508200507.78h11riS-lkp@intel.com> (raw)
In-Reply-To: <20250818095400.1610209-1-vkuznets@redhat.com>

Hi Vitaly,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on arm64/for-next/core tip/master linus/master v6.17-rc2]
[cannot apply to tip/auto-latest next-20250819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Vitaly-Kuznetsov/x86-hyperv-Fix-kdump-on-Azure-CVMs/20250818-175830
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/20250818095400.1610209-1-vkuznets%40redhat.com
patch subject: [PATCH v2] x86/hyperv: Fix kdump on Azure CVMs
config: x86_64-randconfig-101-20250819 (https://download.01.org/0day-ci/archive/20250820/202508200507.78h11riS-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202508200507.78h11riS-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> arch/x86/hyperv/ivm.c:601:2-3: Unneeded semicolon
   arch/x86/hyperv/ivm.c:504:3-4: Unneeded semicolon
   arch/x86/hyperv/ivm.c:561:3-4: Unneeded semicolon

vim +601 arch/x86/hyperv/ivm.c

   565	
   566	void hv_ivm_clear_host_access(void)
   567	{
   568		struct hv_gpa_range_for_visibility *input;
   569		struct hv_enc_pfn_region *ent;
   570		unsigned long flags;
   571		u64 hv_status;
   572		int cur, i;
   573	
   574		if (!hv_is_isolation_supported())
   575			return;
   576	
   577		raw_spin_lock_irqsave(&hv_list_enc_lock, flags);
   578	
   579		input = *this_cpu_ptr(hyperv_pcpu_input_arg);
   580		if (!input)
   581			goto unlock;
   582	
   583		list_for_each_entry(ent, &hv_list_enc, list) {
   584			for (i = 0, cur = 0; i < ent->count; i++) {
   585				input->gpa_page_list[cur] = ent->pfn + i;
   586				cur++;
   587	
   588				if (cur == HV_MAX_MODIFY_GPA_REP_COUNT || i == ent->count - 1) {
   589					input->partition_id = HV_PARTITION_ID_SELF;
   590					input->host_visibility = VMBUS_PAGE_NOT_VISIBLE;
   591					input->reserved0 = 0;
   592					input->reserved1 = 0;
   593					hv_status = hv_do_rep_hypercall(
   594						HVCALL_MODIFY_SPARSE_GPA_PAGE_HOST_VISIBILITY,
   595						cur, 0, input, NULL);
   596					WARN_ON_ONCE(!hv_result_success(hv_status));
   597					cur = 0;
   598				}
   599			}
   600	
 > 601		};
   602	
   603	unlock:
   604		raw_spin_unlock_irqrestore(&hv_list_enc_lock, flags);
   605	}
   606	EXPORT_SYMBOL_GPL(hv_ivm_clear_host_access);
   607	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2025-08-19 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  9:54 [PATCH v2] x86/hyperv: Fix kdump on Azure CVMs Vitaly Kuznetsov
2025-08-19 17:30 ` Michael Kelley
2025-08-21  9:36   ` Vitaly Kuznetsov
2025-08-21 15:45     ` Michael Kelley
2025-08-19 21:19 ` kernel test robot [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=202508200507.78h11riS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=litian@redhat.com \
    --cc=mhklinux@outlook.com \
    --cc=nunodasneves@linux.microsoft.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=prudo@redhat.com \
    --cc=tiala@microsoft.com \
    --cc=vkuznets@redhat.com \
    --cc=wei.liu@kernel.org \
    --cc=x86@kernel.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.