From: Simo Sorce <simo@redhat.com>
To: Chris Perl <cperl@janestreet.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Chris Perl <chris.perl@gmail.com>
Subject: Re: File Read Returns Non-existent Null Bytes
Date: Thu, 26 Feb 2015 10:56:13 -0500 [thread overview]
Message-ID: <1424966173.640.7.camel@willson.usersys.redhat.com> (raw)
In-Reply-To: <CAAih9mgZ5OwWr6Vw1UTGD=Fd6ASyhoifSOVjd7cDjwXxWbftTQ@mail.gmail.com>
On Thu, 2015-02-26 at 10:45 -0500, Chris Perl wrote:
> > Ok, I assume proper use of locking will address the situation and allow
> > readers to get consistent data and not null bytes ?
>
> Yes, trond said this explicitly in one of his earlier replies.
Thank you, my confusion has been cleared.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
next prev parent reply other threads:[~2015-02-26 15:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 20:56 File Read Returns Non-existent Null Bytes Chris Perl
2015-02-23 22:34 ` Trond Myklebust
2015-02-25 17:04 ` Chris Perl
2015-02-25 17:37 ` Trond Myklebust
2015-02-25 21:02 ` Chris Perl
2015-02-25 21:47 ` Trond Myklebust
2015-02-25 21:53 ` Chris Perl
2015-02-25 22:15 ` Trond Myklebust
2015-02-26 12:41 ` Chris Perl
2015-02-26 13:29 ` Trond Myklebust
2015-02-26 13:42 ` Chris Perl
2015-02-26 14:10 ` Chris Perl
2015-02-26 15:22 ` Simo Sorce
2015-02-26 15:34 ` Trond Myklebust
2015-02-26 15:36 ` Simo Sorce
2015-02-26 15:45 ` Chris Perl
2015-02-26 15:56 ` Simo Sorce [this message]
2015-02-27 1:48 ` Harshula
2015-02-27 13:17 ` Chris Perl
2015-02-26 16:00 ` Chris Perl
2015-02-26 23:43 ` Trond Myklebust
2015-02-26 15:37 ` Trond Myklebust
2015-02-27 22:40 ` J. Bruce Fields
2015-02-27 23:33 ` Chuck Lever
2015-03-02 15:19 ` Chris Perl
2015-03-02 15:57 ` Chuck Lever
2015-03-02 20:58 ` J. Bruce Fields
2015-03-02 21:15 ` Chuck Lever
2015-03-03 13:29 ` Chris Perl
2015-03-03 15:30 ` Chuck Lever
2015-03-03 17:44 ` Trond Myklebust
2015-03-03 19:57 ` Chuck Lever
2015-03-02 21:33 ` didier
2015-03-03 9:09 ` Boaz Harrosh
[not found] ` <CAHHaOubVomDJ5uePb7DFGizZ0TBsyC-tJN5p6-RWOYKQC2oxvA@mail.gmail.com>
2015-02-27 20:13 ` Chris Perl
2015-02-25 22:32 ` Chuck Lever
2015-02-26 0:37 ` Trond Myklebust
2015-02-26 0:43 ` Trond Myklebust
2015-02-26 1:27 ` Trond Myklebust
2015-02-26 15:08 ` Chuck Lever
2015-02-26 16:26 ` fsx size error (was: File Read Returns Non-existent Null Bytes) Chuck Lever
2015-02-26 17:27 ` Trond Myklebust
2015-02-26 19:00 ` Chuck Lever
2015-02-26 23:06 ` Trond Myklebust
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=1424966173.640.7.camel@willson.usersys.redhat.com \
--to=simo@redhat.com \
--cc=chris.perl@gmail.com \
--cc=cperl@janestreet.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.