From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: [GIT PULL] FS bugfixes for 3.17-rc2
Date: Thu, 21 Aug 2014 00:32:33 +0200 [thread overview]
Message-ID: <20140820223233.GA6477@quack.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
to get udf, isofs, and ext3 bug fix.
Top of the tree is e6d8fb340f20. The full shortlog is:
Chao Yu (1):
udf: avoid unneeded up_write when fail to add entry in ->symlink
Chin-Tsung Cheng (1):
ext3: Count internal journal as bsddf overhead in ext3_statfs
Jan Kara (1):
isofs: Fix unbounded recursion when processing relocated directories
The diffstat is
fs/ext3/super.c | 5 +++--
fs/isofs/inode.c | 15 ++++++++-------
fs/isofs/isofs.h | 23 +++++++++++++++++++----
fs/isofs/rock.c | 39 ++++++++++++++++++++++++++++-----------
fs/udf/namei.c | 3 ++-
5 files changed, 60 insertions(+), 25 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
reply other threads:[~2014-08-20 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140820223233.GA6477@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 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.