Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935217AbeAKSoF (ORCPT + 1 other); Thu, 11 Jan 2018 13:44:05 -0500 Received: from userp2130.oracle.com ([156.151.31.86]:51810 "EHLO userp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932483AbeAKSoC (ORCPT ); Thu, 11 Jan 2018 13:44:02 -0500 X-Google-Smtp-Source: ACJfBoti2UtnGN75qYjSl2Hg6ngBmD9Ma1PVEiIg/5we+wEdugkPlSC1IMKCQvmZorKxDRPBXPKX6meZmA7Pnbh0zyY= MIME-Version: 1.0 In-Reply-To: References: <20180105175229.GA29834@kroah.com> <20180105204557.GA8839@kroah.com> <20180107104540.GB14783@kroah.com> <20180108074645.GA24062@kroah.com> From: Pavel Tatashin Date: Thu, 11 Jan 2018 13:40:22 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review To: Greg Kroah-Hartman Cc: Andy Lutomirski , Hugh Dickins , Linus Torvalds , Thomas Voegtle , Linux Kernel Mailing List , Andrew Morton , Guenter Roeck , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, stable , Steve Sistare Content-Type: text/plain; charset="UTF-8" X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8771 signatures=668652 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=677 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801110255 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: If it is better to resubmit this patch via git send-email, please let me know. Thank you, Pavel On Thu, Jan 11, 2018 at 1:36 PM, Pavel Tatashin wrote: > I have root caused the memory corruption panics/hangs that I've been > experiencing during boot with the latest 4.4.110 kernel. The problem > as was suspected by Andy Lutomirski is with interaction between PTI > and EFI. It may affect any system that has EFI bios. I have not > verified if it can affect any other kernel beside 4.4.110 > > Attached is the fix for this issue with explanations that Steve > Sistare and I developed.