From: Nikolay Borisov <nborisov@suse.com>
To: Johannes Thumshirn <jthumshirn@suse.de>, David Sterba <dsterba@suse.com>
Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 12/17] btrfs: add boilerplate code for directly including the crypto framework
Date: Fri, 10 May 2019 19:28:43 +0300 [thread overview]
Message-ID: <a19ac81d-870f-5f78-4976-7733a0d1f7b0@suse.com> (raw)
In-Reply-To: <20190510111547.15310-13-jthumshirn@suse.de>
On 10.05.19 г. 14:15 ч., Johannes Thumshirn wrote:
> Add boilerplate code for directly including the crypto framework.
>
> This helps us flipping the switch for new algorithms.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/ctree.h | 11 +++++++++++
> fs/btrfs/disk-io.c | 49 ++++++++++++++++++++++++++++++++++++++++++-------
> 2 files changed, 53 insertions(+), 7 deletions(-)
>
> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> index e62934fb8748..8733c55ed686 100644
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -73,6 +73,7 @@ struct btrfs_ref;
>
> /* four bytes for CRC32 */
> static const int btrfs_csum_sizes[] = { 4 };
> +static char *btrfs_csum_names[] = { "crc32c" };
>
> #define BTRFS_EMPTY_DIR_SIZE 0
>
> @@ -1165,6 +1166,8 @@ struct btrfs_fs_info {
> spinlock_t ref_verify_lock;
> struct rb_root block_tree;
> #endif
> +
> + struct crypto_shash *csum_shash;
> };
>
> static inline struct btrfs_fs_info *btrfs_sb(struct super_block *sb)
> @@ -2452,6 +2455,14 @@ static inline int btrfs_super_csum_size(const struct btrfs_super_block *s)
> return btrfs_csum_sizes[t];
> }
>
> +static inline char *btrfs_super_csum_name(const struct btrfs_super_block *s)
> +{
> + u16 t = btrfs_super_csum_type(s);
> + /*
> + * csum type is validated at mount time
> + */
> + return btrfs_csum_names[t];
> +}
>
> /*
> * The leaf data grows from end-to-front in the node.
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 21ae9daf52b7..d57adf3eaa85 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -19,6 +19,7 @@
> #include <linux/crc32c.h>
> #include <linux/sched/mm.h>
> #include <asm/unaligned.h>
> +#include <crypto/hash.h>
> #include "ctree.h"
> #include "disk-io.h"
> #include "transaction.h"
> @@ -2261,6 +2262,30 @@ static int btrfs_init_workqueues(struct btrfs_fs_info *fs_info,
> return 0;
> }
>
> +static int btrfs_init_csum_hash(struct btrfs_fs_info *fs_info,
> + struct btrfs_super_block *sb)
> +{
> + struct crypto_shash *csum_shash;
> + const char *csum_name = btrfs_super_csum_name(sb);
> +
> + csum_shash = crypto_alloc_shash(csum_name, 0, 0);
> +
> + if (IS_ERR(csum_shash)) {
> + btrfs_err(fs_info, "error allocating %s hash for checksum\n",
> + csum_name);
> + return PTR_ERR(csum_shash);
> + }
> +
> + fs_info->csum_shash = csum_shash;
> +
> + return 0;
> +}
> +
> +static void btrfs_free_csum_hash(struct btrfs_fs_info *fs_info)
> +{
> + crypto_free_shash(fs_info->csum_shash);
> +}
> +
> static int btrfs_replay_log(struct btrfs_fs_info *fs_info,
> struct btrfs_fs_devices *fs_devices)
> {
> @@ -2819,6 +2844,14 @@ int open_ctree(struct super_block *sb,
> goto fail_alloc;
> }
>
> +
> + ret = btrfs_init_csum_hash(fs_info, (struct btrfs_super_block *)
> + bh->b_data);
> + if (ret) {
> + err = ret;
> + goto fail_alloc;
> + }
> +
> /*
> * We want to check superblock checksum, the type is stored inside.
> * Pass the whole disk block of size BTRFS_SUPER_INFO_SIZE (4k).
> @@ -2827,7 +2860,7 @@ int open_ctree(struct super_block *sb,
> btrfs_err(fs_info, "superblock checksum mismatch");
> err = -EINVAL;
> brelse(bh);
> - goto fail_alloc;
> + goto fail_csum;
> }
>
> /*
> @@ -2864,11 +2897,11 @@ int open_ctree(struct super_block *sb,
> if (ret) {
> btrfs_err(fs_info, "superblock contains fatal errors");
> err = -EINVAL;
> - goto fail_alloc;
> + goto fail_csum;
> }
>
> if (!btrfs_super_root(disk_super))
> - goto fail_alloc;
> + goto fail_csum;
>
> /* check FS state, whether FS is broken. */
> if (btrfs_super_flags(disk_super) & BTRFS_SUPER_FLAG_ERROR)
> @@ -2890,7 +2923,7 @@ int open_ctree(struct super_block *sb,
> ret = btrfs_parse_options(fs_info, options, sb->s_flags);
> if (ret) {
> err = ret;
> - goto fail_alloc;
> + goto fail_csum;
> }
>
> features = btrfs_super_incompat_flags(disk_super) &
> @@ -2900,7 +2933,7 @@ int open_ctree(struct super_block *sb,
> "cannot mount because of unsupported optional features (%llx)",
> features);
> err = -EINVAL;
> - goto fail_alloc;
> + goto fail_csum;
> }
>
> features = btrfs_super_incompat_flags(disk_super);
> @@ -2944,7 +2977,7 @@ int open_ctree(struct super_block *sb,
> btrfs_err(fs_info,
> "unequal nodesize/sectorsize (%u != %u) are not allowed for mixed block groups",
> nodesize, sectorsize);
> - goto fail_alloc;
> + goto fail_csum;
> }
>
> /*
> @@ -2960,7 +2993,7 @@ int open_ctree(struct super_block *sb,
> "cannot mount read-write because of unsupported optional features (%llx)",
> features);
> err = -EINVAL;
> - goto fail_alloc;
> + goto fail_csum;
> }
>
> ret = btrfs_init_workqueues(fs_info, fs_devices);
> @@ -3338,6 +3371,8 @@ int open_ctree(struct super_block *sb,
> fail_sb_buffer:
> btrfs_stop_all_workers(fs_info);
> btrfs_free_block_groups(fs_info);
> +fail_csum:
> + btrfs_free_csum_hash(fs_info);
> fail_alloc:
> fail_iput:
> btrfs_mapping_tree_free(&fs_info->mapping_tree);
>
next prev parent reply other threads:[~2019-05-10 16:28 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 11:15 [PATCH 00/17] Add support for SHA-256 checksums Johannes Thumshirn
2019-05-10 11:15 ` [PATCH 01/17] btrfs: use btrfs_csum_data() instead of directly calling crc32c Johannes Thumshirn
2019-05-10 16:16 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 02/17] btrfs: resurrect btrfs_crc32c() Johannes Thumshirn
2019-05-10 16:16 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 03/17] btrfs: use btrfs_crc32c() instead of btrfs_extref_hash() Johannes Thumshirn
2019-05-10 13:03 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 04/17] btrfs: use btrfs_crc32c() instead of btrfs_name_hash() Johannes Thumshirn
2019-05-10 12:56 ` Chris Mason
2019-05-13 7:04 ` Johannes Thumshirn
2019-05-10 11:15 ` [PATCH 05/17] btrfs: don't assume ordered sums to be 4 bytes Johannes Thumshirn
2019-05-10 13:25 ` Nikolay Borisov
2019-05-10 13:27 ` Nikolay Borisov
2019-05-13 7:06 ` Johannes Thumshirn
2019-05-10 11:15 ` [PATCH 06/17] btrfs: dont assume compressed_bio " Johannes Thumshirn
2019-05-10 11:15 ` [PATCH 07/17] btrfs: use btrfs_crc32c{,_final}() in for free space cache Johannes Thumshirn
2019-05-10 13:27 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 08/17] btrfs: format checksums according to type for printing Johannes Thumshirn
2019-05-10 13:28 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 09/17] btrfs: add common checksum type validation Johannes Thumshirn
2019-05-10 13:37 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 10/17] btrfs: check for supported superblock checksum type before checksum validation Johannes Thumshirn
2019-05-10 13:37 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 11/17] btrfs: Simplify btrfs_check_super_csum() and get rid of size assumptions Johannes Thumshirn
2019-05-10 13:41 ` Nikolay Borisov
2019-05-10 11:15 ` [PATCH 12/17] btrfs: add boilerplate code for directly including the crypto framework Johannes Thumshirn
2019-05-10 16:28 ` Nikolay Borisov [this message]
2019-05-10 11:15 ` [PATCH 13/17] btrfs: pass in an fs_info to btrfs_csum_{data,final}() Johannes Thumshirn
2019-05-10 11:15 ` [PATCH 14/17] btrfs: directly call into crypto framework for checsumming Johannes Thumshirn
2019-05-10 13:45 ` Chris Mason
2019-05-10 13:54 ` Chris Mason
2019-05-13 7:17 ` Johannes Thumshirn
2019-05-13 13:55 ` Chris Mason
2019-05-14 12:46 ` Johannes Thumshirn
2019-05-13 13:00 ` David Sterba
2019-05-13 13:01 ` Johannes Thumshirn
2019-05-13 14:30 ` David Sterba
2019-05-10 11:15 ` [PATCH 15/17] btrfs: remove assumption about csum type form btrfs_csum_{data,final}() Johannes Thumshirn
2019-05-13 12:56 ` David Sterba
2019-05-10 11:15 ` [PATCH 16/17] btrfs: remove assumption about csum type form btrfs_print_data_csum_error() Johannes Thumshirn
2019-05-10 11:15 ` [PATCH 17/17] btrfs: add sha256 as another checksum algorithm Johannes Thumshirn
2019-05-10 12:30 ` Nikolay Borisov
2019-05-13 7:11 ` Johannes Thumshirn
2019-05-13 12:54 ` David Sterba
2019-05-13 12:55 ` Johannes Thumshirn
2019-05-15 1:45 ` Jeff Mahoney
2019-05-13 12:55 ` David Sterba
2019-05-13 12:58 ` Johannes Thumshirn
2019-05-15 17:27 ` [PATCH 00/17] Add support for SHA-256 checksums David Sterba
2019-05-16 6:30 ` Paul Jones
2019-05-16 8:16 ` Nikolay Borisov
2019-05-16 8:20 ` Johannes Thumshirn
2019-05-17 18:36 ` Diego Calleja
2019-05-17 19:07 ` Johannes Thumshirn
2019-05-18 0:38 ` Adam Borowski
2019-05-20 7:47 ` Johannes Thumshirn
2019-05-20 11:34 ` Austin S. Hemmelgarn
2019-05-20 11:57 ` Johannes Thumshirn
2019-05-20 11:42 ` Austin S. Hemmelgarn
2019-05-30 12:21 ` 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=a19ac81d-870f-5f78-4976-7733a0d1f7b0@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=jthumshirn@suse.de \
--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).