From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16165] Wrong data returned on read after write if file size was changed with ftruncate before
Date: Fri, 11 Jun 2010 14:26:55 GMT [thread overview]
Message-ID: <201006111426.o5BEQtxh004828@demeter.kernel.org> (raw)
In-Reply-To: <bug-16165-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16165
Frank Mehnert <frank.mehnert@sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |frank.mehnert@sun.com
--- Comment #9 from Frank Mehnert <frank.mehnert@sun.com> 2010-06-11 14:26:51 ---
When compiling the test case, please make sure to add a third parameter to
open(), for example 0777, otherwise it wouldn't compile on Ubuntu (O_CREAT
requires 3 parameters for open).
Executed the testcase here on an up-to-date Ubuntu 10.04 installed on an
ext4-formatted partition. The testcase does NOT fail if the test file already
exists. But it fails about 130 out of 500 times if I remove the test file prior
to each run. When using Linux 2.6.34 vanilla: 7080 out of 10000 runs reported a
corrupted buffer. And, like expected, the test never fails on an ext3
partition.
So please make sure to run the testcase like this:
# for i in `seq 1 500`; do rm -f /mnt/tst; ./aio_corrupt /mnt/tst; done
where /mnt is an ext4 partition.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-06-11 14:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 22:01 [Bug 16165] New: Wrong data returned on read after write if file size was changed with ftruncate before bugzilla-daemon
2010-06-08 22:25 ` [Bug 16165] " bugzilla-daemon
2010-06-08 22:27 ` bugzilla-daemon
2010-06-08 22:29 ` bugzilla-daemon
2010-06-08 22:38 ` bugzilla-daemon
2010-06-09 15:26 ` bugzilla-daemon
2010-06-09 15:49 ` bugzilla-daemon
2010-06-09 22:57 ` bugzilla-daemon
2010-06-10 7:38 ` bugzilla-daemon
2010-06-11 14:26 ` bugzilla-daemon [this message]
2010-06-16 8:19 ` bugzilla-daemon
2010-06-18 15:13 ` bugzilla-daemon
2010-06-18 15:30 ` bugzilla-daemon
2010-06-19 18:10 ` bugzilla-daemon
2010-06-19 18:12 ` bugzilla-daemon
2010-06-24 15:53 ` bugzilla-daemon
2010-06-24 22:20 ` bugzilla-daemon
2010-06-27 9:05 ` bugzilla-daemon
2010-07-23 21:45 ` bugzilla-daemon
2010-07-23 21:51 ` bugzilla-daemon
2010-07-23 22:09 ` bugzilla-daemon
2010-08-04 2:06 ` bugzilla-daemon
2010-08-04 3:40 ` bugzilla-daemon
2010-08-16 13:24 ` bugzilla-daemon
2010-08-16 19:26 ` bugzilla-daemon
2010-08-16 19:59 ` bugzilla-daemon
2010-11-04 11:00 ` bugzilla-daemon
2011-01-10 12:40 ` bugzilla-daemon
2011-04-23 17:42 ` bugzilla-daemon
2012-07-20 12:58 ` bugzilla-daemon
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=201006111426.o5BEQtxh004828@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 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.