Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6887411ybe; Wed, 18 Sep 2019 10:38:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqyj07WnA5uPh3ayhXeHNwpx2QcPD0g+fDvR+LE2ZTi/7IZfcOZ5GXSu/Xl5AvQPUSW/CebH X-Received: by 2002:a50:a5f8:: with SMTP id b53mr11573588edc.39.1568828328729; Wed, 18 Sep 2019 10:38:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568828328; cv=none; d=google.com; s=arc-20160816; b=xw4Q8/sR5r9AOtNpPFvnqCXqQkNl2DvfTWC/QajQ6igOGkIm7oOHJ83oejoU3Ah0+3 vuLCQw3E56MPoodYvXqzTi2jTp+ioqcD1Stz85qoyMmkjZJ5nofvkWxCgxmrhv4kIN7O 5Sg6hAuID8OxIal638lAmcz9MgDAqU3KjBnjf2o6bk0YvLew4WB7AkfdAWb98UZPQTBt 6z+t8s9atBeGlqD3wQfUfNaDylAT5KtSvTLAZs88GxheUE9d1Rn79IoV3EWXadrBmOdk +2M+xKxaNaM5VvhIud2MGa1MAF2FPzNceGbFzWu5YEzmkl44DEEf5sV8eruYgVu91MUd M2Ow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:message-id :subject:cc:to:from:date:dkim-signature; bh=rqP6jsncvb2DgD+nc1vlgeo3QRfZGME7iRqdgV/c0qU=; b=IM21m906odE2O5CYuLi9W0AM3lDHIKDxepWZl6JAL/gYxRQvmRtCLxlEVmcDX34JnQ opSRBY+eQGxU1UMdoWyND+VI3sgZ5VE6GRNdAxwahXXvHCf4re4iemn6D9rzoOvm5fxC +E824MM5k4RjDuZoI+Vo3jCMcFz5wlVe7WLiYLzjENwmWiOQsKqHlFcmHsMh0v4iPIbe XA1hDApIzK+kSZayTANiZPEz9i/ZhbsHfDmDf4RTxMR3Z3pwMg0wCUml1ATNxBrugtpA biSQGGI6uXIKodwr0csOWjspCkbnGZReCQxHewzvpEkcCRfF/QwYeSRlzKQXbTXuyoOy MQZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=15NJGStM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d19si3610966edv.287.2019.09.18.10.38.24; Wed, 18 Sep 2019 10:38:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=15NJGStM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730031AbfIRQGZ (ORCPT + 99 others); Wed, 18 Sep 2019 12:06:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:35544 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727609AbfIRQGY (ORCPT ); Wed, 18 Sep 2019 12:06:24 -0400 Received: from paulmck-ThinkPad-P72 (unknown [50.237.200.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9E0E4208C0; Wed, 18 Sep 2019 16:06:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568822784; bh=ufV+8/UZw+vPMDxNA536wLRDJt1zPivHGmQyve3d8aw=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=15NJGStM4Da4odbjTTHfh/6lBz4MhxmwovCJSvCvLS4Bz3vRQ8UokWtiXuxTvsTb8 X2f4xkjBMTU2ptM2IMkvGGgXIjjEDCXEq90+uXlkQihx9KtGqvAWX23Mk/Cr8g01au 0ubr42g5whT68U+j/17JeotLNHGHDNjZsHLqDBp4= Date: Wed, 18 Sep 2019 09:06:21 -0700 From: "Paul E. McKenney" To: Davidlohr Bueso Cc: Sebastian Andrzej Siewior , linux-kernel@vger.kernel.org, Josh Triplett , Thomas Gleixner Subject: Re: [PATCH] locking: locktorture: Do not include rwlock.h directly Message-ID: <20190918160621.GH30224@paulmck-ThinkPad-P72> Reply-To: paulmck@kernel.org References: <20190916145404.bukcmlliequu77wk@linutronix.de> <20190917071614.kcmux562y6wbskj5@linux-p48b> <20190917170620.GC30224@paulmck-ThinkPad-P72> <20190918062404.hyk5p2gs4mtybl3t@linux-p48b> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190918062404.hyk5p2gs4mtybl3t@linux-p48b> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 17, 2019 at 11:24:04PM -0700, Davidlohr Bueso wrote: > On Tue, 17 Sep 2019, Paul E. McKenney wrote: > > > On Tue, Sep 17, 2019 at 12:16:14AM -0700, Davidlohr Bueso wrote: > > > On Mon, 16 Sep 2019, Sebastian Andrzej Siewior wrote: > > > > > > > From: Wolfgang M. Reimer > > > > > > > > Including rwlock.h directly will cause kernel builds to fail > > > > if CONFIG_PREEMPT_RT is defined. The correct header file > > > > (rwlock_rt.h OR rwlock.h) will be included by spinlock.h which > > > > is included by locktorture.c anyway. > > > > > > > > Remove the include of linux/rwlock.h. > > > > > > > > > > Acked-by: Davidlohr Bueso > > > > Applied, thank you! > > > > But does anyone actually run locktorture? > > I do at least. I also know of cases of other folks making use of the > "framework" to test/pound on custom tailored locks -- ie btrfs tree lock. > > I've also seen it in one or two academic papers. OK, I will hold off on a patch removing it, then. ;-) Thanx, Paul