From: Markus Elfring <Markus.Elfring@web.de>
To: Jia-Ju Bai <baijiaju1990@gmail.com>,
jfs-discussion@lists.sourceforge.net
Cc: Dave Kleikamp <shaggy@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [v2] fs: jfs: fix a possible data race in metapage_writepage()
Date: Tue, 5 May 2020 16:32:13 +0200 [thread overview]
Message-ID: <074b3682-054a-d2ec-8142-1d87e1e97ed6@web.de> (raw)
In-Reply-To: <05f9211d-6f57-b613-b584-a6d84b163645@gmail.com>
>>> This data race is found by our concurrency fuzzer.
>> * How do you think about to replace the word “is” by “was”?
>
> Okay.
Can such a positive feedback influence the change descriptions
for any of your other patches?
Regards,
Markus
next prev parent reply other threads:[~2020-05-05 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:53 [PATCH v2] fs: jfs: fix a possible data race in metapage_writepage() Jia-Ju Bai
2020-05-05 14:15 ` Markus Elfring
2020-05-05 14:21 ` Jia-Ju Bai
2020-05-05 14:32 ` Markus Elfring [this message]
2020-05-05 14:50 ` [v2] " Jia-Ju Bai
2020-05-05 14:27 ` [PATCH v2] " Dave Kleikamp
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=074b3682-054a-d2ec-8142-1d87e1e97ed6@web.de \
--to=markus.elfring@web.de \
--cc=baijiaju1990@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@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;
as well as URLs for NNTP newsgroup(s).