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: [PULL REQUEST] UDF, ext3, isofs fixes for 3.6-rc1
Date: Wed, 25 Jul 2012 00:31:17 +0200 [thread overview]
Message-ID: <20120724223117.GA9508@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 assorted, mostly trivial fixes, for udf, ext2, ext3, and isofs. I'm
on vacation and scarcely checking email since we are expecting baby any day
now but these fixes should be safe to go in and I don't want to delay them
unnecessarily.
Top of the tree is 0143fc5. The full shortlog is:
Artem Bityutskiy (1):
udf: stop using s_dirt
Ashish Sangwan (1):
UDF: Remove unnecessary variable "offset" from udf_fill_inode
Eric Sandeen (1):
ext3: force ro mount if ext3_setup_super() fails
Jan Kara (5):
udf: Fix memory leak when mounting
udf: Do not decrement i_blocks when freeing indirect extent block
jbd: Check return value of blkdev_issue_flush()
ext3: Check return value of blkdev_issue_flush()
udf: Improve table length check to avoid possible overflow
Jeff Liu (1):
quota: fix checkpatch.pl warning by replacing <asm/uaccess.h> with <linux/uaccess.h>
Mathias Krause (2):
isofs: avoid info leak on export
udf: avoid info leak on export
Wanlong Gao (1):
ext2: cleanup the confused goto label
The diffstat is
fs/ext2/super.c | 6 +-
fs/ext3/fsync.c | 9 +++-
fs/ext3/super.c | 3 +-
fs/isofs/export.c | 1 +
fs/jbd/recovery.c | 7 ++-
fs/quota/dquot.c | 2 +-
fs/quota/quota.c | 2 +-
fs/udf/inode.c | 4 --
fs/udf/namei.c | 1 +
fs/udf/super.c | 130 ++++++++++++++++++++++++++--------------------------
fs/udf/truncate.c | 4 +-
fs/udf/udfdecl.h | 1 -
12 files changed, 88 insertions(+), 82 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
reply other threads:[~2012-07-24 22:31 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=20120724223117.GA9508@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).