linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PULL REQUEST] ext2, ext3, udf updates for 3.9-rc1
Date: Tue, 26 Feb 2013 16:15:09 +0100	[thread overview]
Message-ID: <20130226151509.GA8465@quack.suse.cz> (raw)
In-Reply-To: <20130222152507.GD15083@quack.suse.cz>

On Fri 22-02-13 16:25:07, Jan Kara wrote:
>   Hello Linus,
> 
>   could you please pull from
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
> 
>   to get several UDF fixes, a support for UDF extent cache, and couple of
> ext2 and ext3 cleanups and minor fixes.
  Did this get lost somehow? You didn't pull yet and I didn't get any hate
mail from you either ;)...

								Honza

> Top of the tree is 712ddc5. The full shortlog is:
> 
> Guo Chao (1):
>       ext3, ext4, ocfs2: remove unused macro NAMEI_RA_INDEX
> 
> Jan Kara (5):
>       ext3: Fix memory leak when quota options are specified multiple times
>       udf: Write LVID to disk after opening / closing
>       udf: Fix bitmap overflow on large filesystems with small block size
>       udf: Make s_block_bitmap standard array
>       udf: Remove unused s_extLength from udf_bitmap
> 
> Namjae Jeon (1):
>       udf: add extent cache support in case of file reading
> 
> Wang Shilong (9):
>       Ext2: free memory allocated and forget buffer head when io error happens
>       Ext3: add necessary check in case IO error happens
>       Ext2: use unlikely to improve the efficiency of the kernel
>       Ext3: use unlikely to improve the efficiency of the kernel
>       Ext2: return ENOMEM rather than EIO if sb_getblk fails
>       Ext3: return ENOMEM rather than EIO if sb_getblk fails
>       Ext2: remove the overhead check about sb in the function ext2_new_blocks
>       Ext2: mark inode dirty after the function dquot_free_block_nodirty is called
>       Ext2: remove the static function release_blocks to optimize the kernel
> 
> The diffstat is
> 
>  fs/ext2/balloc.c |   28 ++++++-----------
>  fs/ext2/inode.c  |   12 +++++++
>  fs/ext2/super.c  |    2 +-
>  fs/ext2/xattr.c  |    4 +-
>  fs/ext3/inode.c  |   16 ++++++----
>  fs/ext3/namei.c  |    1 -
>  fs/ext3/resize.c |   12 ++++----
>  fs/ext3/super.c  |   51 +++++++++++++++++++-------------
>  fs/ext3/xattr.c  |    4 +-
>  fs/ext4/namei.c  |    1 -
>  fs/ocfs2/dir.c   |    1 -
>  fs/udf/inode.c   |   86 ++++++++++++++++++++++++++++++++++++++++++++++++++----
>  fs/udf/super.c   |   11 ++++---
>  fs/udf/udf_i.h   |   16 ++++++++++
>  fs/udf/udf_sb.h  |    5 +--
>  fs/udf/udfdecl.h |    5 ---
>  16 files changed, 177 insertions(+), 78 deletions(-)
> 
> 							Thanks
> 								Honza
> -- 
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2013-02-26 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 15:25 [PULL REQUEST] ext2, ext3, udf updates for 3.9-rc1 Jan Kara
2013-02-26 15:15 ` Jan Kara [this message]

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=20130226151509.GA8465@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@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).