linux-ext4 - help with 'discard' mount option on ext4

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>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Oct 2013 08:28:20 +0000 (UTC)
From:	Prasanna NAVARATNA <prasanna.navaratna@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: help with 'discard' mount option on ext4

Hello,

I'm using Hynix eMMC4.41 with Linux kernel 3.4.5.

After mounting ext4 partition /userdata with 'discard' mount option enabled,
fs triggers TRIM commands to eMMC after every file deletion. With this
setup, for a continuous reboot test (5s awake and issue reboot and repeat)
with 10 or 20 iterations, i see data corruption in eMMC consistently.

mount options are :- noatime,nosuid,nodev,noauto_da_alloc,discard
encryptable="path"

What am i missing here? if 'discard' mount option is removed, then no data
corruption in eMMC for more than 200 iterations. Does TRIM needs some extra
care? BKOPS is not enabled in eMMC (is bkops mandatory if using TRIM?)
Are there any latest patches which address these corruption issues during
reboot with discard option enabled?
Please help to analyze further.

Thanks,
Prasanna NAVARATNA

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html