From: "홍신 shin hong" <hongshin@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: BUG? a possible bug for the absence of memory barrier
Date: Thu, 10 Sep 2009 00:15:24 +0900 [thread overview]
Message-ID: <2014bcab0909090815jf4929efib21cbf52b963e330@mail.gmail.com> (raw)
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
next reply other threads:[~2009-09-09 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:15 홍신 shin hong [this message]
2009-09-10 20:38 ` BUG? a possible bug for the absence of memory barrier Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2014bcab0909090815jf4929efib21cbf52b963e330@mail.gmail.com \
--to=hongshin@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox