On Wed, Jul 10, 2019 at 01:27:30PM +0200, Stefan Riedmueller wrote: > Due to the recursive ubi_thread implementation in the barebox, a large > amount of wear-leveling can lead to a stack overflow. > > This was observed during extensive ubi stress tests with the linux > kernel and periodic power cycles. We found that if the wear-leveling > threshold is exceeded and a large amount of erase blocks need > wear-leveling the stack can overflow. > > The hardware used to observe this was a phyCORE-i.MX 6 with 1GB NAND flash. > > As the kernel is perfectly capable of handling wear-leveling we can > increase the wear-leveling threshold in the barebox to leave it to the > kernel. To minimize the chance of wear-leveling in the barebox max out > the threshold. I can follow the reasoning and it seems indeed better and more safe to leave the wearleveling to the Kernel. Given that, can't we just disable wear leveling completely in barebox? Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
