Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933114AbdGKPMA (ORCPT ); Tue, 11 Jul 2017 11:12:00 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:46364 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932607AbdGKPLw (ORCPT ); Tue, 11 Jul 2017 11:11:52 -0400 Date: Tue, 11 Jul 2017 16:10:53 +0100 From: Mark Rutland To: Andy Lutomirski Cc: linux-arm-kerne@lists.infradead.org, "linux-kernel@vger.kernel.org" , linux-arch , Catalin Marinas , James Morse , Laura Abbott , Russell King , stable , steve.capper@arm.com, Will Deacon , Al Viro , Peter Zijlstra Subject: Re: [PATCH 0/2] Fatal signal handing within uaccess faults Message-ID: <20170711151053.GG2681@leverpostej> References: <1499782590-31366-1-git-send-email-mark.rutland@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 720 Lines: 22 On Tue, Jul 11, 2017 at 08:04:50AM -0700, Andy Lutomirski wrote: > On Tue, Jul 11, 2017 at 7:16 AM, Mark Rutland wrote: > > Hi, > > > > Arch maintainer tl;dr: most arch fault code doesn't handle fatal signals > > correctly, allowing unprivileged users to create an unkillable task which can > > lock up the system. Please check whether your arch is affected. > > I haven't tested for real, but brief inspection of the code suggests > that x86 is okay. AFAICT, yes. As mentioned later on in the message, I beleive it's been ok since commit: 26178ec11ef3c6c8 ("x86: mm: consolidate VM_FAULT_RETRY handling") ... and my test-case didn't trigger anything in local testing on my desktop. Mark.