From: Keith Mok <ek9852@gmail.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Keith Mok <kmok@cyngn.com>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: Use crypto crc32 functions
Date: Mon, 7 Mar 2016 15:54:24 -0800 [thread overview]
Message-ID: <CAHjoi4fQhyqybO2=QFJScQ=sP4wjdjtMR5EC2TPmWZDQheeGLA@mail.gmail.com> (raw)
In-Reply-To: <20160307233551.GA44902@jaegeuk.gateway>
No, other common filesystem use this BUG_ON in this way, pls read:
fs/btrfs/hash.c
fs/ext4/ext4.h
and even the BUG_ON is used inside crc32c function that is exported by
libcrc32c.c which xfs and many other drivers are using:
lib/libcrc32c.c
fs/xfs/libxfs/xfs_cksum.h
If it should have some fallback mechanism, it should be done inside
the crypto_shash_update function, rather than scatter all over to
their users.
Thanks.
2016-03-07 15:35 GMT-08:00 Jaegeuk Kim <jaegeuk@kernel.org>:
> On Wed, Mar 02, 2016 at 12:01:02PM -0800, Keith Mok wrote:
>> Will update the first BUG_ON by using SHASH_DESC_ON_STACK.
>
> I meant, for *every* BUG_ONs, doing like:
>
> if (err)
> return original f2fs_crc32();
>
> Thanks,
>
>>
>>
>> 2016-03-02 10:21 GMT-08:00 Jaegeuk Kim <jaegeuk@kernel.org>:
>> > Hi Keith,
>> >
>> >> +static inline __u32 f2fs_crc32(struct f2fs_sb_info *sbi, const void *address,
>> >> + unsigned int length)
>> >> +{
>> >> + struct {
>> >> + struct shash_desc shash;
>> >> + char ctx[4];
>> >> + } desc;
>> >> + int err;
>> >> +
>> >> + BUG_ON(crypto_shash_descsize(sbi->s_chksum_driver) != sizeof(desc.ctx));
>> >
>> > I can't accept this and the below BUG_ON, since this hits during the checkpoint
>> > procedure which is very critical for entire filesystem.
>> > How about calling back the original method for the error cases?
>> >
>> > Thanks,
>> >
>> >> +
>> >> + desc.shash.tfm = sbi->s_chksum_driver;
>> >> + desc.shash.flags = 0;
>> >> + *(u32 *)desc.ctx = F2FS_SUPER_MAGIC;
>> >> +
>> >> + err = crypto_shash_update(&desc.shash, address, length);
>> >> + BUG_ON(err);
>> >> +
>> >> + return *(__u32 *)desc.ctx;
>> >> +}
>> >> +
>> >> +static inline bool f2fs_crc_valid(struct f2fs_sb_info *sbi, __u32 blk_crc,
>> >> + void *buf, size_t buf_size)
>> >> +{
>> >> + return f2fs_crc32(sbi, buf, buf_size) == blk_crc;
>> >> +}
>> >> +
>> >> static inline struct f2fs_inode_info *F2FS_I(struct inode *inode)
>> >> {
>> >> return container_of(inode, struct f2fs_inode_info, vfs_inode);
>> >> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> >> index 6134832..9630865 100644
>> >> --- a/fs/f2fs/super.c
>> >> +++ b/fs/f2fs/super.c
>> >> @@ -574,6 +574,8 @@ static void f2fs_put_super(struct super_block *sb)
>> >> wait_for_completion(&sbi->s_kobj_unregister);
>> >>
>> >> sb->s_fs_info = NULL;
>> >> + if (sbi->s_chksum_driver)
>> >> + crypto_free_shash(sbi->s_chksum_driver);
>> >> kfree(sbi->raw_super);
>> >> kfree(sbi);
>> >> }
>> >> @@ -1254,6 +1256,15 @@ try_onemore:
>> >> if (!sbi)
>> >> return -ENOMEM;
>> >>
>> >> + /* Load the checksum driver */
>> >> + sbi->s_chksum_driver = crypto_alloc_shash("crc32", 0, 0);
>> >> + if (IS_ERR(sbi->s_chksum_driver)) {
>> >> + f2fs_msg(sb, KERN_ERR, "Cannot load crc32 driver.");
>> >> + err = PTR_ERR(sbi->s_chksum_driver);
>> >> + sbi->s_chksum_driver = NULL;
>> >> + goto free_sbi;
>> >> + }
>> >> +
>> >> /* set a block size */
>> >> if (unlikely(!sb_set_blocksize(sb, F2FS_BLKSIZE))) {
>> >> f2fs_msg(sb, KERN_ERR, "unable to set blocksize");
>> >> @@ -1506,6 +1517,8 @@ free_options:
>> >> free_sb_buf:
>> >> kfree(raw_super);
>> >> free_sbi:
>> >> + if (sbi->s_chksum_driver)
>> >> + crypto_free_shash(sbi->s_chksum_driver);
>> >> kfree(sbi);
>> >>
>> >> /* give only one another chance */
>> >> --
>> >> 2.5.1
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
next prev parent reply other threads:[~2016-03-07 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 23:12 [PATCH] f2fs: Use crypto crc32 functions Keith Mok
2016-03-01 9:19 ` Chao Yu
2016-03-01 16:52 ` Keith Mok
2016-03-02 18:21 ` Jaegeuk Kim
2016-03-02 20:01 ` Keith Mok
2016-03-07 23:35 ` Jaegeuk Kim
2016-03-07 23:54 ` Keith Mok [this message]
2016-03-08 1:04 ` Jaegeuk Kim
2016-03-02 20:04 ` [PATCH v2] f2fs: Use cryptoapi " Keith Mok
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='CAHjoi4fQhyqybO2=QFJScQ=sP4wjdjtMR5EC2TPmWZDQheeGLA@mail.gmail.com' \
--to=ek9852@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=kmok@cyngn.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).