summaryrefslogtreecommitdiffstats
path: root/common/console.c
diff options
context:
space:
mode:
authorStefan Riedmueller <s.riedmueller@phytec.de>2019-09-20 13:35:19 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2019-10-14 12:52:11 +0200
commitd1210dc63f38e7e6d8147b44b3f6f9518c099306 (patch)
tree82febde62f5ae5694a608f6582e4e1fdc016cad0 /common/console.c
parent003737566584dc1bed4ddfcde17c9d59e58073c1 (diff)
downloadbarebox-d1210dc63f38e7e6d8147b44b3f6f9518c099306.tar.gz
barebox-d1210dc63f38e7e6d8147b44b3f6f9518c099306.tar.xz
mtd: ubi: Max out wear-leveling threshold
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 disable wear-leveling in the barebox by maxing out the threshold and removing its Kconfig option. Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'common/console.c')
0 files changed, 0 insertions, 0 deletions