From: Stefani Seibold <stefani@seibold.net>
To: Xiao Guangrong <guangrong.xiao@gmail.com>, paulmck@linux.vnet.ibm.com
Cc: peterz@infradead.org, rostedt@goodmis.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Is read barrier missed in kfifo?
Date: Fri, 11 May 2018 09:33:06 +0200 [thread overview]
Message-ID: <1526023986.28429.1.camel@seibold.net> (raw)
In-Reply-To: <5382d3a8-08e0-5429-0cd3-36f9c69197e1@gmail.com>
My guts thinks you are right. Feel free to send a patch...
Am Freitag, den 11.05.2018, 15:25 +0800 schrieb Xiao Guangrong:
> Hi,
>
> Currently, there is no read barrier between reading the index
> (kfifo.in) and fetching the real data from the fifo.
>
> I am afraid that will cause the vfifo is observed as not empty
> however the data is not actually ready for read. Right?
>
> Thanks!
next prev parent reply other threads:[~2018-05-11 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 7:25 Is read barrier missed in kfifo? Xiao Guangrong
2018-05-11 7:33 ` Stefani Seibold [this message]
2018-05-11 8:32 ` Peter Zijlstra
2018-05-11 16:20 ` Paul E. McKenney
2018-05-14 6:57 ` Peter Zijlstra
2018-05-14 13:25 ` Paul E. McKenney
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=1526023986.28429.1.camel@seibold.net \
--to=stefani@seibold.net \
--cc=guangrong.xiao@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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