We guarantee that the write is committed all-or-nothing, but do rely onPurely from a design point of view, I feel we are breaking atomicity and
userspace not issuing racing atomic writes or racing regular writes.
I can easily change this, as I mentioned, but I am not convinced that it is
a must.
hence we should serialize or just stop userspace from doing this (which
is a bit extreme).
I know userspace should ideally not do overwriting atomic writes but if
it is something we are allowing (which we do) then it is
kernel's responsibility to ensure atomicity. Sure we can penalize them
by serializing the writes but not by tearing it.
With that reasoning, I don't think the test should accomodate for this
particular scenario.