From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755838AbcI0R5f (ORCPT ); Tue, 27 Sep 2016 13:57:35 -0400 Received: from foss.arm.com ([217.140.101.70]:52768 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753345AbcI0R50 (ORCPT ); Tue, 27 Sep 2016 13:57:26 -0400 Date: Tue, 27 Sep 2016 18:57:20 +0100 From: Mark Rutland To: Josh Poimboeuf , Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, Andrew Morton , Eric Dumazet , Ingo Molnar , Jiri Slaby , Peter Zijlstra Subject: Re: [PATCH 0/3] Kill off show_stack() NULL-implies-current idiom Message-ID: <20160927175720.GA4479@remoulade> References: <1474902979-18436-1-git-send-email-mark.rutland@arm.com> <20160926200136.sbltg4tp5uft4yfo@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160926200136.sbltg4tp5uft4yfo@treble> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 26, 2016 at 03:01:36PM -0500, Josh Poimboeuf wrote: > On Mon, Sep 26, 2016 at 04:16:16PM +0100, Mark Rutland wrote: > > Today, show_stack() accepts a NULL task parameter, which it takes to mean the > > current task. However, as noted in tip/x86/asm commit: > > > > 81539169f283329f ("x86/dumpstack: Remove NULL task pointer convention") > > > > ... having a NULL task parameter imply current leads to subtle bugs in stack > > walking code (so far seen on both 86 and arm64), makes callsites harder to > > read, and is unnecessary as all callers have access to current. > > > > As a step towards removing the problematic NULL-implies-current idiom entirely, > > these patches ensure that generic code explictly passes current to > > show_stack(), rather than relying on arch code to handle NULL. > > This is a good step, though it would be really nice to fix this > tree-wide. Do you have any plans to do so? I started having a go, and in doing so I've realised that as things stand, these patches are broken, as some architectures don't handle current explicitly. Please disregard all patches in this series. Apologies, Mark.