[PATCH v3] mtd: Verify written data in paranoid mode
Richard Weinberger
richard at nod.at
Mon May 12 05:47:05 PDT 2025
----- Ursprüngliche Mail -----
> Von: "Csókás Bence" <csokas.bence at prolan.hu>
> Well, yes, in our case. But the point is, we have a strict requirement
> for data integrity, which is not unique to us I believe. I would think
> there are other industrial control applications like ours, which dictate
> a high data integrity.
In your last patch set you said your hardware has an issue that every
now and that data is not properly written.
Now you talk about data integrity requirements. I'm confused.
My point is that at some level we need to trust hardware,
if your flash memory is so broken that you can't rely on the write
path you're in deep trouble.
What is the next step, reading it back every five seconds to make
sure it is still there? (just kidding).
We do have plenty of tests to verify this for *testing*
to find broken drivers or hardware.
e.g. mtd/ubi tests, UBI verify at runtime.
Thanks,
//richard
More information about the linux-mtd
mailing list