From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([198.137.202.133]:35978 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725868AbeJ2FUi (ORCPT ); Mon, 29 Oct 2018 01:20:38 -0400 Date: Sun, 28 Oct 2018 13:34:47 -0700 From: Christoph Hellwig To: Peter Zijlstra Cc: Dave Chinner , Bart Van Assche , Alexander Viro , linux-fsdevel@vger.kernel.org, Johannes Berg , Ingo Molnar , Theodore Ts'o Subject: Re: [PATCH RFC] kernel/locking, fs/direct-io: Introduce and use down_write_nolockdep() Message-ID: <20181028203447.GA9330@infradead.org> References: <20181026164905.214474-1-bvanassche@acm.org> <20181027053745.GI6311@dastard> <20181028175840.GA744@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181028175840.GA744@hirez.programming.kicks-ass.net> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Oct 28, 2018 at 06:58:40PM +0100, Peter Zijlstra wrote: > Also, from a quick look, this has been broken for donkeys years, > right? That comment: > > /* will be released by direct_io_worker */ > > has been there since 2009. Back then of course it was a mutex, and the > curious thing is, mutexes have _never_ supported this release from > another context thing. direct_io_worker back then was just a helper called by __blockdev_direct_IO in the same context. But yes, this comment is horribly out of date.