linux-kernel - Re: [PATCH 4.11 00/28] 4.11.1-stable review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <efa3b911-93f6-29b4-a9ca-e0d9b480a4ef@osg.samsung.com>
Date:   Fri, 12 May 2017 10:01:41 -0600
From:   Shuah Khan <shuahkh@....samsung.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, matt@...eblueprint.co.uk
Cc:     torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        linux@...ck-us.net, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, stable@...r.kernel.org
Subject: Re: [PATCH 4.11 00/28] 4.11.1-stable review

On 05/12/2017 09:25 AM, Shuah Khan wrote:
> On 05/11/2017 08:12 AM, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 4.11.1 release.
>> There are 28 patches in this series, all will be posted as a response
>> to this one.  If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Sat May 13 14:12:05 UTC 2017.
>> Anything received after that time might be too late.
>>
>> The whole patch series can be found in one patch at:
>> 	kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.11.1-rc1.gz
>> or in the git tree and branch at:
>>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.11.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>>
> 
> Compiled and booted on my test system. No dmesg regressions.
> 
> thanks,
> -- Shuah
> 

Greg/Matt,

I started seeing this maybe since 4.11, so it isn't really a 4.11.1
issue, however sounds like this shouldn't be an error message, since
it is showing up on an older platform.

efi: EFI_MEMMAP is not enabled.
efi: Failed to lookup EFI memory descriptor for 0x00000000d9e0f018


>From 816e76129ed5fadd28e526c43397c79775194b5c Mon Sep 17 00:00:00 2001
From: Matt Fleming <matt@...eblueprint.co.uk>
Date: Mon, 29 Feb 2016 21:22:52 +0000
Subject: [PATCH] efi: Allow drivers to reserve boot services forever

This change was introduced in Commit: 816e76129ed5fadd28e526c43397c79775194b5c

Matt!

Shouldn't this be a debug message?? Is this a really an error??

thanks,
-- Shuah