All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Sterba <dsterba@suse.cz>
Cc: stable@vger.kernel.org, Josef Bacik <jbacik@fusionio.com>,
	Chris Mason <chris.mason@fusionio.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: Handful of btrfs fixes for 3.11.x stable
Date: Sat, 5 Oct 2013 16:52:18 -0700	[thread overview]
Message-ID: <20131005235218.GG18223@kroah.com> (raw)
In-Reply-To: <20130920165301.GA11262@kroah.com>

On Fri, Sep 20, 2013 at 09:53:02AM -0700, Greg KH wrote:
> On Fri, Sep 20, 2013 at 06:34:39PM +0200, David Sterba wrote:
> > Hi stable team,
> > 
> > please add the following commits to 3.11 tree, they fix user visible problems,
> > were tested and are now present in 3.12-rc1.
> > 
> > 3d05ca371200b3366530621abf73769024581b79
> > b13a004528c3e5eb060a26eee795f5a0da7bfe9f
> > 7ef67ffda91cc0c56f33937bfdf1d057b9ee96ca
> > ca6d07c1d74bf7ba3083bc31a9aeeaa1d0ad86aa

These git commit ids don't match up to anything in Linus's tree, where
did you get them from?

> > Josef Bacik (4):
> >   Btrfs: reset ret in record_one_backref
> >   Btrfs: change how we queue blocks for backref checking
> >   Btrfs: skip subvol entries when checking if we've created a dir already
> >   Btrfs: remove ourselves from the cluster list under lock

I can dig through the tree to find these, but I'd prefer if you could
provide the correct ids to verify I got them right.

Also, what order do I apply them in?

thanks,

greg k-h

  parent reply	other threads:[~2013-10-06  6:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 16:34 Handful of btrfs fixes for 3.11.x stable David Sterba
2013-09-20 16:53 ` Greg KH
2013-09-23 16:56   ` David Sterba
2013-10-01 17:03   ` David Sterba
2013-10-01 17:49     ` Greg KH
2013-10-02  1:15       ` Chris Mason
2013-10-02  5:01         ` Greg KH
2013-10-05 23:52   ` Greg KH [this message]
2013-10-07 20:34     ` Josef Bacik
2013-10-10 23:23       ` Greg KH
2013-09-20 19:34 ` Chris Mason

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=20131005235218.GG18223@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris.mason@fusionio.com \
    --cc=dsterba@suse.cz \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@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.