Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933947AbcKVTmW (ORCPT ); Tue, 22 Nov 2016 14:42:22 -0500 Received: from mail-io0-f193.google.com ([209.85.223.193]:34521 "EHLO mail-io0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933856AbcKVTmV (ORCPT ); Tue, 22 Nov 2016 14:42:21 -0500 MIME-Version: 1.0 In-Reply-To: <20161122193720.GA3045@worktop.programming.kicks-ass.net> References: <20161122095715.GN3092@twins.programming.kicks-ass.net> <20161122193720.GA3045@worktop.programming.kicks-ass.net> From: Linus Torvalds Date: Tue, 22 Nov 2016 11:42:19 -0800 X-Google-Sender-Auth: 0ErmTy6AVn7WqzVLtoMMrjR2u-o Message-ID: Subject: Re: [RFC][PATCH] x86: Verify access_ok() context To: Peter Zijlstra Cc: Andy Lutomirski , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" 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: 344 Lines: 11 On Tue, Nov 22, 2016 at 11:37 AM, Peter Zijlstra wrote: > > CONFIG_DEBUG_VM seems somehow inappropriate. The usual might_fault() logic? That uses defined(CONFIG_PROVE_LOCKING) || defined(CONFIG_DEBUG_ATOMIC_SLEEP) (and "might_sleep()" uses just CONFIG_DEBUG_ATOMIC_SLEEP, maybe that's fine). Linus