ACK/cmnt: [PULL][unstable][Artful][SRU Zesty] arm64: fix crash reading from /proc/kcore

[dann frazier]

On Wed, Jul 12, 2017 at 2:18 AM, Stefan Bader
<stefan.bader at canonical.com> wrote:
> On 06.07.2017 23:55, dann frazier wrote:
>> See:
>> BugLink: https://bugs.launchpad.net/bugs/1702749
>>
>> The following changes since commit f4f26263ff6a66c2012e9417a56e1b01a95c45d0:
>>
>>   UBUNTU: Ubuntu-4.10.0-28.32 (2017-06-29 11:24:09 +0200)
>>
>> are available in the git repository at:
>>
>>   git://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux lp1702749
>>
>> for you to fetch changes up to a1d4967053e162bf4933b5a62b7be3490c3ba882:
>>
>>   arm64: mm: select CONFIG_ARCH_PROC_KCORE_TEXT (2017-07-06 13:53:23 -0600)
>>
>> ----------------------------------------------------------------
>> Ard Biesheuvel (2):
>>       fs/proc: kcore: use kcore_list type to check for vmalloc/module address
>>       arm64: mm: select CONFIG_ARCH_PROC_KCORE_TEXT
>>
>>  arch/arm64/Kconfig | 3 +++
>>  fs/proc/kcore.c    | 2 +-
>>  2 files changed, 4 insertions(+), 1 deletion(-)
>>
> Acked-by: Stefan Bader <stefan.bader at canonical.com>
>
> Looks reasonable, did not find any fixups related to the kcore patch. Might need
> an updateconfigs check when applying to Zesty.

Thanks Stefan. fyi, I ran an updateconfigs in zesty & didn't see any changes.

> <whine>Could be a little more
> descriptive in the pull-request</whine>

Yeah, I do go back & forth on what to put in the pull-request since I
try to capture everything in the bug. Perhaps I can just cut & paste
the bug description/SRU template in future PRs?

  -dann