From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Zero from EOF instead of next block
Date: Mon, 14 Feb 2011 14:25:25 -0800 [thread overview]
Message-ID: <20110214222524.GD8413@noexit> (raw)
In-Reply-To: <AANLkTikPdMgJWexFbBx8fRKxwAoKGsbiYkHR49Kfk90=@mail.gmail.com>
On Mon, Feb 14, 2011 at 04:16:37PM -0600, Goldwyn Rodrigues wrote:
> Oh, I thought the test case was self-explanatory. The test case first writes
> a lot of dirty data on disk "0xbaadfeed", syncs the data and removes
> the file so that the filesystem has a lot of "0xbaadfeed" data on it.
>
> The second executable writes records of 32 bytes and seeks another 32
> bytes. While reading the file back, 0xbaadfeed is read when zeros are
> expected. The program shows where the unexpected data is found.
>
> So, for holes not spanning extents or even blocks, the data which was
> on disk previously shows up.
That shouldn't happen, of course. But the solution will not be
writing past the last block of the file. We should be catching it
instead when extending the i_size into a previously uninitialized block.
Joel
--
"One of the symptoms of an approaching nervous breakdown is the
belief that one's work is terribly important."
- Bertrand Russell
http://www.jlbec.org/
jlbec at evilplan.org
next prev parent reply other threads:[~2011-02-14 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 6:21 [Ocfs2-devel] [PATCH] Zero from EOF instead of next block Goldwyn Rodrigues
2011-02-14 7:25 ` Joel Becker
2011-02-14 18:24 ` Goldwyn Rodrigues
2011-02-14 22:00 ` Joel Becker
2011-02-14 22:02 ` Joel Becker
2011-02-14 22:16 ` Goldwyn Rodrigues
2011-02-14 22:25 ` Joel Becker [this message]
2011-02-16 6:26 ` Goldwyn Rodrigues
2011-02-16 14:24 ` Goldwyn Rodrigues
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=20110214222524.GD8413@noexit \
--to=jlbec@evilplan.org \
--cc=ocfs2-devel@oss.oracle.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.