From: kbuild test robot <lkp@intel.com>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, thomas.lendacky@amd.com,
dyoung@redhat.com
Subject: Re: [PATCH 2/2 V2] Support kdump when AMD secure memory encryption is active
Date: Thu, 14 Jun 2018 20:55:06 +0800 [thread overview]
Message-ID: <201806142024.WDGkcZ5I%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180614084748.9617-3-lijiang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
Hi Lianbo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17 next-20180614]
[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/20180614-164938
config: i386-randconfig-c0-06141337 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/proc/vmcore.o: In function `read_from_oldmem':
>> fs/proc/vmcore.c:127: undefined reference to `copy_oldmem_page_encrypted'
vim +127 fs/proc/vmcore.c
100
101 /* Reads a page from the oldmem device from given offset. */
102 static ssize_t read_from_oldmem(char *buf, size_t count,
103 u64 *ppos, int userbuf,
104 bool encrypted)
105 {
106 unsigned long pfn, offset;
107 size_t nr_bytes;
108 ssize_t read = 0, tmp;
109
110 if (!count)
111 return 0;
112
113 offset = (unsigned long)(*ppos % PAGE_SIZE);
114 pfn = (unsigned long)(*ppos / PAGE_SIZE);
115
116 do {
117 if (count > (PAGE_SIZE - offset))
118 nr_bytes = PAGE_SIZE - offset;
119 else
120 nr_bytes = count;
121
122 /* If pfn is not ram, return zeros for sparse dump files */
123 if (pfn_is_ram(pfn) == 0)
124 memset(buf, 0, nr_bytes);
125 else {
126 if (encrypted)
> 127 tmp = copy_oldmem_page_encrypted(pfn, buf,
128 nr_bytes, offset, userbuf);
129 else
130 tmp = copy_oldmem_page(pfn, buf, nr_bytes,
131 offset, userbuf);
132
133 if (tmp < 0)
134 return tmp;
135 }
136 *ppos += nr_bytes;
137 count -= nr_bytes;
138 buf += nr_bytes;
139 read += nr_bytes;
140 ++pfn;
141 offset = 0;
142 } while (count);
143
144 return read;
145 }
146
---
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: 30191 bytes --]
next prev parent reply other threads:[~2018-06-14 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 8:47 [PATCH 0/2 V2] Support kdump for AMD secure memory encryption(sme) Lianbo Jiang
2018-06-14 8:47 ` [PATCH 1/2 V2] Add a function(ioremap_encrypted) for kdump when AMD sme enabled Lianbo Jiang
2018-06-14 8:47 ` [PATCH 2/2 V2] Support kdump when AMD secure memory encryption is active Lianbo Jiang
2018-06-14 8:56 ` Dave Young
2018-06-15 8:17 ` Dave Young
2018-06-14 12:55 ` kbuild test robot [this message]
2018-06-14 13:59 ` lijiang
2018-06-14 13:01 ` kbuild test robot
2018-06-14 19:24 ` kbuild test robot
2018-06-15 7:19 ` Dave Young
2018-06-15 11:43 ` 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=201806142024.WDGkcZ5I%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dyoung@redhat.com \
--cc=kbuild-all@01.org \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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®