Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932404AbdDDWMa (ORCPT ); Tue, 4 Apr 2017 18:12:30 -0400 Received: from mail-pg0-f53.google.com ([74.125.83.53]:34529 "EHLO mail-pg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932275AbdDDWMZ (ORCPT ); Tue, 4 Apr 2017 18:12:25 -0400 From: Kees Cook To: Ingo Molnar Cc: Kees Cook , Peter Zijlstra , "Paul E. McKenney" , Kalle Valo , Andrew Morton , Rik van Riel , Jakub Kicinski , Viresh Kumar , Andy Shevchenko , Geert Uytterhoeven , Olof Johansson , Chris Wilson , George Spelvin , Thomas Gleixner , Josh Poimboeuf , David Windsor , linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: [PATCH v2] bug: further enhance use of CHECK_DATA_CORRUPTION Date: Tue, 4 Apr 2017 15:12:11 -0700 Message-Id: <1491343938-75336-1-git-send-email-keescook@chromium.org> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 603 Lines: 14 This continues in applying the CHECK_DATA_CORRUPTION tests where appropriate, and pulling similar CONFIGs under the same check. Most notably, this adds the checks to refcount_t so that system builders can Oops their kernels when encountering a potential refcounter attack. (And so now the LKDTM tests for refcount issues pass correctly.) The series depends on the changes in -next made to lib/refcount.c, so it might be easiest if this goes through the locking tree... v2 is a rebase to -next and adjusts to using WARN_ONCE() instead of WARN(). -Kees v1 was here: https://lkml.org/lkml/2017/3/6/720