Hello. I am reporting possible bugs caused
by the absence of memory barriers.

Please examine this issue and let me know your opinion.

In add_async_extent(), an async_extent object is allocated and initialized
and then links to &cow->extents.

However, since there is no memory barrier
between the initialization and the linking to the list,
these two operations are executed opposite order.
And the re-ordering might result race condition.

The similar issue is also in join_transaction().

Thank you

Sincerely

Shin Hong
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to