All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Matthew Wilcox <willy@infradead.org>,
	stable@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [4.19-stable PATCH] dax: Avoid losing wakeup in dax_lock_mapping_entry
Date: Thu, 29 Nov 2018 09:04:30 +0100	[thread overview]
Message-ID: <20181129080430.GB13859@kroah.com> (raw)
In-Reply-To: <154343119877.981933.9776503138356369421.stgit@dwillia2-desk3.amr.corp.intel.com>

On Wed, Nov 28, 2018 at 10:53:44AM -0800, Dan Williams wrote:
> From: Matthew Wilcox <willy@infradead.org>
> 
> 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: <stable@vger.kernel.org>
> Signed-off-by: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> Passes the nvdimm unit test suite which exercises the lock path.

Now applied, thanks.

greg k-h
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: stable@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
	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
Date: Thu, 29 Nov 2018 09:04:30 +0100	[thread overview]
Message-ID: <20181129080430.GB13859@kroah.com> (raw)
In-Reply-To: <154343119877.981933.9776503138356369421.stgit@dwillia2-desk3.amr.corp.intel.com>

On Wed, Nov 28, 2018 at 10:53:44AM -0800, Dan Williams wrote:
> From: Matthew Wilcox <willy@infradead.org>
> 
> 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: <stable@vger.kernel.org>
> Signed-off-by: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> Passes the nvdimm unit test suite which exercises the lock path.

Now applied, thanks.

greg k-h

  reply	other threads:[~2018-11-29  8:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 10:40 FAILED: patch "[PATCH] dax: Avoid losing wakeup in dax_lock_mapping_entry" failed to apply to 4.19-stable tree gregkh
2018-11-26 12:22 ` Matthew Wilcox
2018-11-26 12:22   ` Matthew Wilcox
2018-11-26 14:27   ` Matthew Wilcox
2018-11-26 14:27     ` Matthew Wilcox
2018-11-28 18:53     ` [4.19-stable PATCH] dax: Avoid losing wakeup in dax_lock_mapping_entry Dan Williams
2018-11-28 18:53       ` Dan Williams
2018-11-29  8:04       ` Greg KH [this message]
2018-11-29  8:04         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181129080430.GB13859@kroah.com \
    --to=greg@kroah.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=stable@vger.kernel.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.