Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933262AbdGKPFa (ORCPT ); Tue, 11 Jul 2017 11:05:30 -0400 Received: from mail-vk0-f41.google.com ([209.85.213.41]:34357 "EHLO mail-vk0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933190AbdGKPF0 (ORCPT ); Tue, 11 Jul 2017 11:05:26 -0400 MIME-Version: 1.0 In-Reply-To: <1499782590-31366-1-git-send-email-mark.rutland@arm.com> References: <1499782590-31366-1-git-send-email-mark.rutland@arm.com> From: Andy Lutomirski Date: Tue, 11 Jul 2017 08:04:50 -0700 Message-ID: Subject: Re: [PATCH 0/2] Fatal signal handing within uaccess faults To: Mark Rutland 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 Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 401 Lines: 11 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. --Andy