All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: neilb@suse.de, a3at.mail@gmail.com, axboe@fb.com, hch@lst.de,
	stable@vger.kernel.org, stable-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Patch "block: destroy bdi before blockdev is unregistered." has been added to the 4.0-stable tree
Date: Fri, 15 May 2015 16:16:32 -0700	[thread overview]
Message-ID: <20150515231632.GA23048@kroah.com> (raw)
In-Reply-To: <20150515070323.GA1540@swordfish>

On Fri, May 15, 2015 at 04:03:23PM +0900, Sergey Senozhatsky wrote:
> On (05/14/15 19:18), gregkh@linuxfoundation.org wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >     block: destroy bdi before blockdev is unregistered.
> > 
> > to the 4.0-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      block-destroy-bdi-before-blockdev-is-unregistered.patch
> > and it can be found in the queue-4.0 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> > 
> > 
> 
> Hello Greg,
> 
> jfi, I think this commit will WARN_ON(). fixed by https://lkml.org/lkml/2015/5/8/29
> 
> 
> (https://lkml.org/lkml/2015/4/28/568)

That site isn't working for me, what is the git commit id of the fix for
this in Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2015-05-15 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  2:18 Patch "block: destroy bdi before blockdev is unregistered." has been added to the 4.0-stable tree gregkh
2015-05-15  7:03 ` Sergey Senozhatsky
2015-05-15 23:16   ` Greg KH [this message]
2015-05-16  1:39     ` NeilBrown
2015-05-19  5:33       ` Christoph Hellwig

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=20150515231632.GA23048@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=a3at.mail@gmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.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.