From: Adrian Hunter <adrian.hunter@nokia.com>
To: "홍신 shin hong" <hongshin@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS: possible bug for the absence of memory barrier
Date: Wed, 09 Sep 2009 17:35:40 +0300 [thread overview]
Message-ID: <4AA7BD3C.7080302@nokia.com> (raw)
In-Reply-To: <2014bcab0909090722t101657b1vf698607aae62e53e@mail.gmail.com>
홍신 shin hong wrote:
> Hello. I am reporting the possible bugs caused by absence of memory barriers.
>
> Since I do not have much background,
> I can not convince that the codes are buggy.
> But I hope that this report is helpful.
> Please examine the issue and let me know your opinion.
>
> In add_replay_bud() of UBIFS in Linux 2.6.30.5, it newly allocate a bud_entry
> object and initialize and then link it to the replay_buds list.
>
> The last initialization operation is "b->sqnum = sqnum ;" and
> the linking to the list "list_add_tail(&b->list, &c->replay_buds;".
>
> However, since there is no memory barrier between these two,
> the execution order might be changed
> so that uninitialized data might be accessible to other threads.
>
> Therefore, race condition might occur and it may result error.
>
> Please examine this issue.
> Thank you
>
> Sincerely
> Shin Hong
A race is not possible because there is only one thread that can be
replaying because it is only done when mounting.
prev parent reply other threads:[~2009-09-09 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 14:22 UBIFS: possible bug for the absence of memory barrier 홍신 shin hong
2009-09-09 14:35 ` Adrian Hunter [this message]
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=4AA7BD3C.7080302@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=hongshin@gmail.com \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.