From: "zhengbin (A)" <zhengbin13@huawei.com>
To: Dave Chinner <david@fromorbit.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
<linux-xfs@vger.kernel.org>
Cc: <yi.zhang@huawei.com>
Subject: Questions about CVE-2016-8660
Date: Thu, 5 Mar 2020 16:30:16 +0800 [thread overview]
Message-ID: <2cb951f9-bd4e-a182-e7d3-6a903ff49535@huawei.com> (raw)
Recently I am studying CVE-2016-8660, in https://seclists.org/oss-sec/2016/q4/118,
it says that this bug is introduced by commit fc0561cefc04 ("xfs: optimise away log forces on timestamp updates for fdatasync").
And in https://patchwork.kernel.org/patch/9363339/#19693745, david correction has nothing to do with this commit,
and is a page lock order bug in the XFS seek hole/data implementation(demsg is in http://people.redhat.com/qcai/tmp/dmesg-sync,
Unfortunately, it is not accessible now, I do not understand why this is a page lock order bug).
Is this CVE solved? Can I see the demsg in other way? thanks.
next reply other threads:[~2020-03-05 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 8:30 zhengbin (A) [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-05 8:28 Questions about CVE-2016-8660 zhengbin (A)
2020-03-05 21:27 ` Dave Chinner
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=2cb951f9-bd4e-a182-e7d3-6a903ff49535@huawei.com \
--to=zhengbin13@huawei.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=yi.zhang@huawei.com \
/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