From: kbuild test robot <lkp@intel.com>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: thomas.lendacky@amd.com, jroedel@suse.de, brijesh.singh@amd.com,
bhe@redhat.com, tiwai@suse.de, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, kbuild-all@01.org,
baiyaowei@cmss.chinamobile.com, hpa@zytor.com,
bhelgaas@google.com, tglx@linutronix.de, bp@suse.de,
dyoung@redhat.com, akpm@linux-foundation.org,
dan.j.williams@intel.com
Subject: Re: [PATCH v8 RESEND 4/4] kdump/vmcore: support encrypted old memory with SME enabled
Date: Sun, 30 Sep 2018 12:22:38 +0800 [thread overview]
Message-ID: <201809301217.24Vlt4g0%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180930031033.22110-5-lijiang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2252 bytes --]
Hi Lianbo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on sof-driver-fuweitax/master]
[also build test ERROR on v4.19-rc5 next-20180928]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Lianbo-Jiang/Support-kdump-for-AMD-secure-memory-encryption-SME/20180930-112044
base: https://github.com/fuweitax/linux master
config: x86_64-randconfig-x005-201839 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> arch/x86//kernel/crash_dump_64.c:93:9: error: redefinition of 'copy_oldmem_page_encrypted'
ssize_t copy_oldmem_page_encrypted(unsigned long pfn, char *buf, size_t csize,
^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from arch/x86//kernel/crash_dump_64.c:10:0:
include/linux/crash_dump.h:34:9: note: previous definition of 'copy_oldmem_page_encrypted' was here
ssize_t copy_oldmem_page_encrypted(unsigned long pfn, char *buf, size_t csize,
^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/copy_oldmem_page_encrypted +93 arch/x86//kernel/crash_dump_64.c
78
79 /**
80 * copy_oldmem_page_encrypted - copy one page from "old memory encrypted"
81 * @pfn: page frame number to be copied
82 * @buf: target memory address for the copy; this can be in kernel address
83 * space or user address space (see @userbuf)
84 * @csize: number of bytes to copy
85 * @offset: offset in bytes into the page (based on pfn) to begin the copy
86 * @userbuf: if set, @buf is in user address space, use copy_to_user(),
87 * otherwise @buf is in kernel address space, use memcpy().
88 *
89 * Copy a page from "old memory encrypted". For this page, there is no pte
90 * mapped in the current kernel. We stitch up a pte, similar to
91 * kmap_atomic.
92 */
> 93 ssize_t copy_oldmem_page_encrypted(unsigned long pfn, char *buf, size_t csize,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28437 bytes --]
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-10-01 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 3:10 [PATCH v8 RESEND 0/4] Support kdump for AMD secure memory encryption(SME) Lianbo Jiang
2018-09-30 3:10 ` [PATCH v8 RESEND 1/4] x86/ioremap: add a function ioremap_encrypted() to remap kdump old memory Lianbo Jiang
2018-09-30 3:10 ` [PATCH v8 RESEND 2/4] kexec: allocate decrypted control pages for kdump in case SME is enabled Lianbo Jiang
2018-09-30 3:10 ` [PATCH v8 RESEND 3/4] iommu/amd: Remap the device table of IOMMU with the memory encryption mask for kdump Lianbo Jiang
2018-09-30 3:10 ` [PATCH v8 RESEND 4/4] kdump/vmcore: support encrypted old memory with SME enabled Lianbo Jiang
2018-09-30 4:22 ` kbuild test robot [this message]
2018-09-30 8:37 ` [PATCH v9 " lijiang
2018-10-01 20:22 ` Borislav Petkov
2018-10-02 11:40 ` [PATCH v8 RESEND 0/4] Support kdump for AMD secure memory encryption(SME) Borislav Petkov
2018-10-03 3:57 ` lijiang
2018-10-03 11:34 ` Borislav Petkov
2018-10-04 9:33 ` lijiang
2018-10-04 19:02 ` Borislav Petkov
2018-10-05 5:52 ` lijiang
2018-10-06 9:56 ` Borislav Petkov
2018-10-07 6:09 ` lijiang
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=201809301217.24Vlt4g0%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tiwai@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox