linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Chris Mason <chris.mason@fusionio.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs fixes
Date: Wed, 23 Jan 2013 09:28:21 +0800	[thread overview]
Message-ID: <20130123012818.GA17162@liubo.jp.oracle.com> (raw)
In-Reply-To: <20130123004833.GA30526@shiny>

On Tue, Jan 22, 2013 at 07:48:33PM -0500, Chris Mason wrote:
> Hi Linus,
> 
> My for-linus branch has our batch of btrfs fixes:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
> 
> We've been hammering away at a crc corruption as well, which I was
> really hoping to get into this pull.  It isn't nailed down yet, but we
> were finally able to get a solid way to reproduce.  The only good
> news is it isn't a recent regression.
> 
> The most important batch of fixes in here come from Ilya.  They address
> a regression Liu Bo found in the balance ioctls for pausing and resuming
> a running balance across drives.
> 
> Josef's orphan truncate patch fixes an obscure corruption we'd see
> during xfstests.
> 
> Arne's patches address problems with subvolume quotas.  If the user
> destroys quota groups incorrectly the FS will refuse to mount.
> 
> The rest are smaller fixes and plugs for memory leaks.

Hi,

Any chance to get these in this round?  I think they're good fixes,
a memory leak and a warning fix, both are got from xfstests.

- Btrfs: use right range to find checksum for compressed extents
  https://patchwork.kernel.org/patch/1937031/
- Btrfs: fix memory leak on extent map after fsync
  https://patchwork.kernel.org/patch/1946561/

thanks,
liubo

> 
> Ilya Dryomov (6) commits (+94/-32):
>     Btrfs: reorder locks and sanity checks in btrfs_ioctl_defrag (+9/-8)
>     Btrfs: fix "mutually exclusive op is running" error code (+4/-4)
>     Btrfs: fix a regression in balance usage filter (+8/-1)
>     Btrfs: bring back balance pause/resume logic (+71/-17)
>     Btrfs: fix unlock order in btrfs_ioctl_rm_dev (+1/-1)
>     Btrfs: fix unlock order in btrfs_ioctl_resize (+1/-1)
> 
> Liu Bo (4) commits (+18/-7):
>     Btrfs: fix a bug when llseek for delalloc bytes behind prealloc extents (+14/-6)
>     Btrfs: let allocation start from the right raid type (+1/-1)
>     Btrfs: reset path lock state to zero (+2/-0)
>     Btrfs: fix off-by-one in lseek (+1/-0)
> 
> Miao Xie (4) commits (+15/-7):
>     Btrfs: fix missing write access release in btrfs_ioctl_resize() (+1/-0)
>     Btrfs: do not delete a subvolume which is in a R/O subvolume (+5/-5)
>     Btrfs: fix resize a readonly device (+4/-2)
>     Btrfs: disable qgroup id 0 (+5/-0)
> 
> Arne Jansen (2) commits (+19/-1):
>     Btrfs: prevent qgroup destroy when there are still relations (+12/-1)
>     Btrfs: ignore orphan qgroup relations (+7/-0)
> 
> Josef Bacik (2) commits (+39/-16):
>     Btrfs: add orphan before truncating pagecache (+38/-15)
>     Btrfs: set flushing if we're limited flushing (+1/-1)
> 
> Zach Brown (1) commits (+1/-0):
>     btrfs: fix btrfs_cont_expand() freeing IS_ERR em
> 
> Lukas Czerner (1) commits (+1/-1):
>     btrfs: get the device in write mode when deleting it
> 
> Eric Sandeen (1) commits (+14/-3):
>     btrfs: update timestamps on truncate()
> 
> Tsutomu Itoh (1) commits (+3/-1):
>     Btrfs: fix memory leak in name_cache_insert()
> 
> Total: (22) commits
> 
>  fs/btrfs/extent-tree.c |   6 ++-
>  fs/btrfs/file.c        |  10 ++--
>  fs/btrfs/inode.c       |  82 +++++++++++++++++++++++--------
>  fs/btrfs/ioctl.c       | 129 +++++++++++++++++++++++++++++++++++--------------
>  fs/btrfs/qgroup.c      |  20 +++++++-
>  fs/btrfs/send.c        |   4 +-
>  fs/btrfs/volumes.c     |  21 ++++++--
>  7 files changed, 204 insertions(+), 68 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-01-23  1:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23  0:48 [GIT PULL] Btrfs fixes Chris Mason
2013-01-23  1:28 ` Liu Bo [this message]
2013-01-23  1:40   ` Chris Mason
2013-01-24 21:52 ` Chris Mason
2013-01-25  3:13   ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2017-01-13 22:01 Chris Mason
2015-11-05 11:20 fdmanana
2015-11-05 14:59 ` Chris Mason
2015-05-15 19:11 Chris Mason
2015-05-01 14:08 Chris Mason
2015-04-26 13:18 Chris Mason
2015-03-20 16:55 Chris Mason
2015-01-23 18:49 Chris Mason
2015-01-08 18:28 Chris Mason
2014-11-01 16:05 Chris Mason
2014-09-19 19:47 Chris Mason
2013-03-17 12:34 Chris Mason
2013-02-07  0:13 Chris Mason
2013-02-07  0:09 Chris Mason
2012-10-26 14:19 Chris Mason
2012-05-06 13:35 Chris Mason
2012-04-28 12:27 Chris Mason
2012-01-27 16:34 Chris Mason
2012-01-27 16:31 Chris Mason
2011-12-23 17:24 Chris Mason
2011-12-16 17:53 Chris Mason
2011-12-16 18:20 ` Chris Mason
2011-12-16 18:29 ` nobody
2011-12-08 19:24 Chris Mason
2011-11-22  1:30 Chris Mason
2011-11-11 21:40 Chris Mason
2011-09-19 23:57 Chris Mason
2011-09-20 16:19 ` Sage Weil
2011-07-08 18:55 [GIT PULL] btrfs fixes Chris Mason
2011-07-11 11:31 ` Tarkan Erimer
2010-04-12 20:00 [GIT PULL] Btrfs fixes 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=20130123012818.GA17162@liubo.jp.oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).