Hi Seunguk,
thank you for your further explanation.
Does it means that only driver with Queued TRIM are affected, or it
affect all TRIM-capable driver?
What I wounder is that, if it is only a timing-triggered problem, why it
is only apparent on specific SSDs? I would expect it to manifest on
other devices also, albeit with different frequency.
Sorry if some questions sound dumb, I'm only trying to understand.
Thanks.
On 24/07/15 14:19, Seunguk Shin wrote:
Gionatan,
Because it is related with timing.
1st trim is issued and before complete it, 2nd trim is started
(allocates memory but is not issued to device)
Then, when 1st trim is completed, it frees 2nd trim's memory,
because they share the pointer due to bug.
If 3rd trim is started before 2nd trim is issued to device,
3rd trim can allocate the same memory with 2nd trim,
because it is freed when 1st trim is completed.
Only this case makes the corruption.
Thank you,
Seunguk Shin
Hi, any idea on why the bug affects/manifests only on specific SATA SSDs?
It is timing related, or it depends on how the controller manage TRIM
requests?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx GPG public key ID: FF5F32A8
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at
http://vger.kernel.org/majordomo-info.html
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx
GPG public key ID: FF5F32A8
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
