From: Jakob Unterwurzacher <jakobunt@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: tmpfs returns incorrect data on concurrent pread() and truncate()
Date: Fri, 4 Nov 2016 00:45:17 +0100 [thread overview]
Message-ID: <2f38a759-33b1-86e8-5929-084ae7e0094b@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1611011602340.1362@eggly.anvils>
First of all, thanks for your replies!
On 02.11.2016 00:51, Hugh Dickins wrote:
> I don't think that there will be much appetite for changing the
> kernel's VFS to prevent that. I hope that gocryptfs can provide
> the serialization that it needs for itself, or otherwise handle
> those zeroes without crashing.
Yes, I dropped the nonce sanity check, the MAC will catch the corruption
anyway.
Just FYI, xfstests generic/075 discovered this. The test itself does not check
the data it gets back, which is why it usually passes.
Best regards,
Jakob
prev parent reply other threads:[~2016-11-03 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:05 Jakob Unterwurzacher
2016-11-01 23:51 ` Hugh Dickins
2016-11-02 1:01 ` Dave Chinner
2016-11-02 1:38 ` Hugh Dickins
2016-11-02 4:01 ` Dave Chinner
2016-11-02 13:21 ` Theodore Ts'o
2016-11-03 23:45 ` Jakob Unterwurzacher [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=2f38a759-33b1-86e8-5929-084ae7e0094b@gmail.com \
--to=jakobunt@gmail.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®