From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: [PATCH 0/3] btrfs-progs: Avoid uninitialized data in output of btrfs-convert
Date: Tue, 8 Sep 2015 21:16:48 +0800 [thread overview]
Message-ID: <cover.1441718128.git.zhaolei@cn.fujitsu.com> (raw)
sequence, transid and reserved field of inode was write to disk
with uninitizlized value, this patchset fixed it, also fixed some
other typo.
Zhao Lei (3):
btrfs-progs: fix set_get typo of btrfs_inode_item->sequence
btrfs-progs: Avoid uninitialized data in output of btrfs-convert
btrfs-progs: add ext2fs_close_inode_scan to copy_inodes
btrfs-convert.c | 5 +++++
ctree.h | 4 +++-
2 files changed, 8 insertions(+), 1 deletion(-)
--
1.8.5.1
next reply other threads:[~2015-09-08 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 13:16 Zhao Lei [this message]
2015-09-08 13:16 ` [PATCH 1/3] btrfs-progs: fix set_get typo of btrfs_inode_item->sequence Zhao Lei
2015-09-08 13:16 ` [PATCH 2/3] btrfs-progs: Avoid uninitialized data in output of btrfs-convert Zhao Lei
2015-09-08 13:16 ` [PATCH 3/3] btrfs-progs: add ext2fs_close_inode_scan to copy_inodes Zhao Lei
2015-09-09 15:41 ` [PATCH 0/3] btrfs-progs: Avoid uninitialized data in output of btrfs-convert David Sterba
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=cover.1441718128.git.zhaolei@cn.fujitsu.com \
--to=zhaolei@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.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).