ubifs_scan: corrupt empty space

[Brian Hill <brian@houston-radar.com>]

One of our systems using Atmel ARM A5, Micron MT29F4G08ABADAWP -w- kernel 3.17 produced this error, which proved unrecoverable:

UBIFS error (pid 452): ubifs_scan: corrupt empty space at LEB 2670:125358
UBIFS error (pid 452): ubifs_scanned_corruption: corruption at LEB 2670:125358
UBIFS error (pid 452): ubifs_scanned_corruption: first 1618 bytes from LEB 2670:125358
00000000: fffffffd ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff

There have been various threads on this type of error over the years, such as:
http://lists.infradead.org/pipermail/linux-mtd/2012-January/039254.html

The most notable comment being:

> ubifs expect empty space to be protected by ecc. But if empty page ecc is not
> ff, this need hack in the nand driver.

I find that no, the atmel driver, unlike some others, doesn't attempt to "correct" erased pages which contain bit flips.
Is the driver still the preferred place to address this issue?  What if the erased space has more bit flips than the ECC strength of the device?  It seems like that block should simply be retired - it has no actual user data.  Will UBIFS handle this particular condition?

I thought I might try and answer "what would happen?" myself with the nandsim kernel module, but I find it can't provide bitflips in erased data - they are always simulated as "perfect".

Thanks for any input,
-Brian Hill