Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936289AbdCVTdU (ORCPT ); Wed, 22 Mar 2017 15:33:20 -0400 Received: from mga01.intel.com ([192.55.52.88]:14731 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934729AbdCVTcK (ORCPT ); Wed, 22 Mar 2017 15:32:10 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,206,1486454400"; d="scan'208";a="63780522" Subject: Re: [PATCH 5/6] notifiers: Use CHECK_DATA_CORRUPTION() on checks To: Kees Cook References: <1488827386-87193-1-git-send-email-keescook@chromium.org> <1488827386-87193-6-git-send-email-keescook@chromium.org> Cc: Andrew Morton , Rik van Riel , "Paul E. McKenney" , Jakub Kicinski , Viresh Kumar , Ingo Molnar , Thomas Gleixner , Dmitry Vyukov , Olof Johansson , Peter Zijlstra , Josh Poimboeuf , LKML , "kernel-hardening@lists.openwall.com" From: Arjan van de Ven Message-ID: <9cb537f0-bae3-3c64-dab0-c0484694876f@linux.intel.com> Date: Wed, 22 Mar 2017 12:32:03 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 471 Lines: 12 On 3/22/2017 12:29 PM, Kees Cook wrote: >> When performing notifier function pointer sanity checking, allow >> CONFIG_BUG_ON_DATA_CORRUPTION to upgrade from a WARN to a BUG. >> Additionally enables CONFIG_DEBUG_NOTIFIERS when selecting >> CONFIG_BUG_ON_DATA_CORRUPTION. > Any feedback on this change? By default, this retains the existing > WARN behavior... if you're upgrading, is the end point really a panic() ? e.g. do you assume people to also set panic-on-oops?