From: David Sterba <dsterba@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, linux-btrfs@vger.kernel.org, clm@fb.com,
jbacik@fb.com, Liu Bo <bo.li.liu@oracle.com>,
Filipe David Borba Manana <fdmanana@gmail.com>
Subject: Re: Btrfs stable updates for 3.12
Date: Thu, 19 Dec 2013 14:08:51 +0100 [thread overview]
Message-ID: <20131219130851.GF6498@suse.cz> (raw)
In-Reply-To: <20131218205154.GG16267@kroah.com>
On Wed, Dec 18, 2013 at 12:51:54PM -0800, Greg KH wrote:
> On Wed, Dec 18, 2013 at 04:14:02PM +0100, David Sterba wrote:
> > Hi,
> >
> > please queue the following patches to 3.12 stable. They fix a few
> > crashes or lockups that were reported by users.
> >
> > The patch "stop using vfs_read in send" may seem big for stable, but without it
> > the send/receive ioctl hits the global open file limit sooner or later,
> > depending on the ram size.
> >
> > Subjects:
> > Btrfs: do a full search everytime in btrfs_search_old_slot
> > Btrfs: reset intwrite on transaction abort
> > Btrfs: fix memory leak of chunks' extent map
> > Btrfs: fix hole check in log_one_extent [bug 66661]
> > Btrfs: fix incorrect inode acl reset
> > Btrfs: stop using vfs_read in send
> > Btrfs: take ordered root lock when removing ordered operations inode
> > Btrfs: do not run snapshot-aware defragment on error
> > Btrfs: fix a crash when running balance and defrag concurrently
> > Btrfs: fix lockdep error in async commit
> > Commits:
> > d4b4087c43cc00a196c5be57fac41f41309f1d56
> > e0228285a8cad70e4b7b4833cc650e36ecd8de89
> > 7d3d1744f8a7d62e4875bd69cc2192a939813880
> > ed9e8af88e2551aaa6bf51d8063a2493e2d71597
> > 8185554d3eb09d23a805456b6fa98dcbb34aa518
> > ed2590953bd06b892f0411fc94e19175d32f197a
> > 93858769172c4e3678917810e9d5de360eb991cc
> > 6f519564d7d978c00351d9ab6abac3deeac31621
> > 48ec47364b6d493f0a9cdc116977bf3f34e5c3ec
> > b1a06a4b574996692b72b742bf6e6aa0c711a948
> >
> > all apply cleanly on top of 3.12.5.
>
> all now applied, along with 4 of these that seem to be applicable to
> 3.10-stable.
Yes, the 4 from stable-queue/3.10 are ok for 3.10, and for 3.11 if that
matters.
Thanks,
david
next prev parent reply other threads:[~2013-12-19 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 15:14 Btrfs stable updates for 3.12 David Sterba
2013-12-18 20:51 ` Greg KH
2013-12-19 13:08 ` David Sterba [this message]
2013-12-19 14:43 ` Luis Henriques
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=20131219130851.GF6498@suse.cz \
--to=dsterba@suse.cz \
--cc=bo.li.liu@oracle.com \
--cc=clm@fb.com \
--cc=fdmanana@gmail.com \
--cc=greg@kroah.com \
--cc=jbacik@fb.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.