The ext4 file is broken in AndroidKK4.4.3 on MX6Q-SABRE-SD

[yuuki]

Dear all,

We run Android4 .4.3 on MX6Q-SABRE-SD board.
Android is booted from eMMC.

We turn off an AC power directly without using Shutdown of Android.
In this case EXT4 file is sometimes broken.

We found the description of the following URL.

http://www.phoronix.com/scan.php?page=news_item&px=Linux-4-EXT4-RAID-Issue-Found
http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ
https://linux.slashdot.org/story/12/10/24/1848203/ext4-data-corruption-bug-hits-linux-kernel

Are these Bug measures included in AndroidKK4 .4.3 BSP?

Best Regards,

Yuuki

[joanxie]

I found we reported ext4 issue as below:

"Kernel will panic with below log after factory reset:
EXT4-fs error (device mmcblk1p4): ext4_validate_block_bitmap:380: comm init: bg 17: block 557056: invalid block bitmap Aborting journal on device mmcblk1p4-8.
Kernel panic - not syncing: EXT4-fs (device mmcblk1p4): panic forced after error Rebooting in 5 seconds..

The root cause is the data type conversion issue.
When a 32-bit data mutiply a 32-bit data, it will still get a 32-bit data.
The 64-bit offset will be cut to 32 bit"

this issue is fixed in the latest android version.

[yuuki]

joanxie‌

Dear Joan Xie-san,

I'm sorry to press you about this, how about the situation afterward?
Your kind helps would be greatly appreciated.

Best Regards,

Yuuki

[yuuki]

joanxie‌

Dear Joan Xie-san,

Thank you for your response.

> this issue is fixed in the latest android version.
=>
Does this mean Android M6?
Or is it Andorid N7?

Would you tell me the modified point for this issue?
We want to backport it in AndroidKK4.4.3.

Best Regards,
Yuuki