linux-kernel - Disadvantage of using yaffs checkpointing ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <cf70f0211003011801r33027ec8s78c9326f9d058c46@mail.gmail.com>
Date:	Mon, 1 Mar 2010 18:01:08 -0800
From:	Shivdas Gujare <shivdas.tech@...il.com>
To:	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Disadvantage of using yaffs checkpointing ?

Hi All,

I am very new to mtd & yaffs and working on boottime optimization and
found that yaffs checkpointing helps to mount
yaffs2 very quickly. I tried it, and was able to save almost 4sec for
128MB partitioned nand.

Since everything looks very good If I use yaffs checkpointing feature
but have a doubt, are there any disadvantage of using check-pointing
by default in final product?

I understood that, check-pointing only disables boot time nand block
scanning & marking it bad if found,
and takes "system snapshot" while using "umount /dev/mtdblockN" which
it use in next boot.
So, If I decided to use "checkpointing" with "umount" while powering
off the device in final product,
are there going to be any problems I will face avoiding block scanning?

Thanks lot for any help.

Thanks and Regards,
Shivdas Gujare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/