From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761006AbbA3XoI (ORCPT ); Fri, 30 Jan 2015 18:44:08 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:49206 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750842AbbA3XoE (ORCPT ); Fri, 30 Jan 2015 18:44:04 -0500 Date: Fri, 30 Jan 2015 15:44:03 -0800 From: Andrew Morton To: Slava Pestov Cc: Peter Zijlstra , Ingo Molnar , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Slava Pestov Subject: Re: [PATCH] taint on lockdep warning with new TAINT_LOCKDEP Message-Id: <20150130154403.fd0dce1675598e9755f7404b@linux-foundation.org> In-Reply-To: <1422568226-18449-1-git-send-email-sp@daterainc.com> References: <1422568226-18449-1-git-send-email-sp@daterainc.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 Jan 2015 13:50:26 -0800 Slava Pestov wrote: > This helps when writing automated tests, since they can fail the > test if the kernel was tainted instead of manually scraping dmesg > for interesting strings. Seems sane. It wouldn't hurt to mention this in Documentation/locking/lockdep-design.txt