From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PATCH 0/4] More mount-time checks
Date: Fri, 7 Nov 2014 17:47:00 +0100 [thread overview]
Message-ID: <cover.1415378049.git.dsterba@suse.cz> (raw)
This series adds more superblock checks that turned out not to be enough after
"btrfs: add more superblock checks". Would be good to get them into 3.18 as I'd
like to submit them to stable kernels as well. This is not easily possible
right now as it depends on a patch that's not merged yet (mentioned below).
Based on current master plus patch
"btrfs: fix typos in btrfs_check_super_valid"
(https://patchwork.kernel.org/patch/5206401/)
David Sterba (4):
btrfs: more superblock checks, lower bounds on devices and
sectorsize/nodesize
btrfs: add checks for sys_chunk_array sizes
btrfs: cleanup, rename a few variables in btrfs_read_sys_array
btrfs: add more checks to btrfs_read_sys_array
fs/btrfs/disk-io.c | 38 +++++++++++++++++++++++++++++++++++++
fs/btrfs/volumes.c | 55 +++++++++++++++++++++++++++++++++++++-----------------
2 files changed, 76 insertions(+), 17 deletions(-)
--
1.8.4.5
next reply other threads:[~2014-11-07 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 16:47 David Sterba [this message]
2014-11-07 16:47 ` [PATCH 1/4] btrfs: more superblock checks, lower bounds on devices and sectorsize/nodesize David Sterba
2014-11-07 16:47 ` [PATCH 2/4] btrfs: add checks for sys_chunk_array sizes David Sterba
2014-11-07 16:47 ` [PATCH 3/4] btrfs: cleanup, rename a few variables in btrfs_read_sys_array David Sterba
2014-11-07 16:47 ` [PATCH 4/4] btrfs: add more checks to btrfs_read_sys_array 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.1415378049.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--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