Return-Path: Date: Thu, 29 Nov 2018 09:04:30 +0100 From: Greg KH To: Dan Williams Cc: stable@vger.kernel.org, Matthew Wilcox , linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [4.19-stable PATCH] dax: Avoid losing wakeup in dax_lock_mapping_entry Message-ID: <20181129080430.GB13859@kroah.com> References: <20181126142743.GA25618@bombadil.infradead.org> <154343119877.981933.9776503138356369421.stgit@dwillia2-desk3.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <154343119877.981933.9776503138356369421.stgit@dwillia2-desk3.amr.corp.intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Nov 28, 2018 at 10:53:44AM -0800, Dan Williams wrote: > From: Matthew Wilcox > > commit 25bbe21bf427a81b8e3ccd480ea0e1d940256156 upstream. > > After calling get_unlocked_entry(), you have to call > put_unlocked_entry() to avoid subsequent waiters losing wakeups. > > Fixes: c2a7d2a11552 ("filesystem-dax: Introduce dax_lock_mapping_entry()") > Cc: > Signed-off-by: Matthew Wilcox > Signed-off-by: Dan Williams > --- > Passes the nvdimm unit test suite which exercises the lock path. Now applied, thanks. greg k-h