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
Subject: Re: [GIT PULL] Quota, reiserfs, udf updates for 3.17-rc1
Date: Tue, 12 Aug 2014 12:45:06 +0200	[thread overview]
Message-ID: <20140812104506.GA4393@quack.suse.cz> (raw)
In-Reply-To: <20140811113803.GE29526@quack.suse.cz>

On Mon 11-08-14 13:38:03, 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 scalability improvements for quota, a few reiserfs fixes, and couple
> of misc cleanups (udf, ext2).
  Jeff Mahoney has found that my patch "reiserfs: Avoid warning from
unlock_new_inode()" is unnecessarily complicating the code since the real
problem is somewhere else than I thought. And since you didn't pull yet
it's unnecessary to have that patch in and then clean it up in another
patch. So just scratch this pull request and I'll send you a new one without
the problematic patch in a while. Sorry for confusion.

								Honza
> 
> Top of the tree is 20601c5299c8. The full shortlog is:
> 
> Andy Shevchenko (1):
>       fs/udf: re-use hex_asc_upper_{hi,lo} macros
> 
> Chao Yu (1):
>       udf: avoid redundant memcpy when writing data in ICB
> 
> Fabian Frederick (2):
>       udf: use linux/uaccess.h
>       fs/quota: kernel-doc warning fixes
> 
> Himangi Saraogi (1):
>       fs/ext2/super.c: Drop memory allocation cast
> 
> Jan Kara (2):
>       reiserfs: Avoid warning from unlock_new_inode()
>       reiserfs: Fix use after free in journal teardown
> 
> Jeff Mahoney (1):
>       reiserfs: fix corruption introduced by balance_leaf refactor
> 
> Niu Yawei (5):
>       quota: missing lock in dqcache_shrink_scan()
>       quota: protect Q_GETFMT by dqonoff_mutex
>       quota: avoid unnecessary dqget()/dqput() calls
>       quota: simplify remove_inode_dquot_ref()
>       quota: remove dqptr_sem
> 
> The diffstat is
> 
>  fs/ext2/super.c        |   2 +-
>  fs/quota/dquot.c       | 182 +++++++++++++++++++++++--------------------------
>  fs/quota/kqid.c        |   2 +-
>  fs/quota/netlink.c     |   3 +-
>  fs/quota/quota.c       |   6 +-
>  fs/reiserfs/do_balan.c | 111 +++++++++++++++++-------------
>  fs/reiserfs/journal.c  |  22 ++++--
>  fs/reiserfs/lbalance.c |   5 +-
>  fs/reiserfs/namei.c    |  41 ++++++-----
>  fs/reiserfs/reiserfs.h |   9 +--
>  fs/reiserfs/super.c    |   6 +-
>  fs/super.c             |   1 -
>  fs/udf/file.c          |  22 +-----
>  fs/udf/lowlevel.c      |   2 +-
>  fs/udf/super.c         |   2 +-
>  fs/udf/symlink.c       |   2 +-
>  fs/udf/unicode.c       |   9 ++-
>  include/linux/quota.h  |   1 -
>  18 files changed, 216 insertions(+), 212 deletions(-)
> 
> 							Thanks
> 								Honza
> -- 
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2014-08-12 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 11:38 [GIT PULL] Quota, reiserfs, udf updates for 3.17-rc1 Jan Kara
2014-08-12 10:45 ` 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=20140812104506.GA4393@quack.suse.cz \
    --to=jack@suse.cz \
    --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).