From: Philip Li <philip.li@intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] xen/pvh: add missing prototype to header
Date: Sat, 20 Nov 2021 10:24:19 +0800 [thread overview]
Message-ID: <YZhcU3e0imdoKV7w@rli9-dbox> (raw)
In-Reply-To: <0c654659-b010-791f-78e7-769108934ce2@intel.com>
On Fri, Nov 19, 2021 at 08:47:49AM -0800, Dave Hansen wrote:
> On 11/19/21 7:39 AM, Juergen Gross wrote:
> > The prototype of mem_map_via_hcall() is missing in its header, so add
> > it.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Fixes: a43fb7da53007e67ad ("xen/pvh: Move Xen code for getting mem map via hcall out of common file")
> > Signed-off-by: Juergen Gross <jgross@suse.com>
>
> $ git describe a43fb7da53007e67ad
> v4.20-rc6-5-ga43fb7da5300
>
> Better late than never, I guess. I wonder what made 0day find this now.
hi Dave, we recently find some unexpected failures for certain bisections,
with the fix, such failures are rerun to see whether we can successfully detect
bad commits, which i think this resulted in extra but late finding on old
commit on mainline. We will keep scan our bisection process to further improve
it to reduce this kind late reporting.
>
> I also guess the one mem_map_via_hcall() call site just used the __weak
> definition so it didn't cause problems if there wasn't a declaration in
> the header.
next prev parent reply other threads:[~2021-11-20 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 15:39 Juergen Gross
2021-11-19 16:47 ` Dave Hansen
2021-11-20 2:24 ` Philip Li [this message]
2021-11-19 22:25 ` Boris Ostrovsky
2021-11-22 22:04 ` Boris Ostrovsky
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=YZhcU3e0imdoKV7w@rli9-dbox \
--to=philip.li@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®