From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 55651] Non-atomic short write problem with O_APPEND
Date: Mon, 25 Mar 2013 20:59:31 +0000 (UTC) [thread overview]
Message-ID: <20130325205931.D140F11FB35@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55651-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=55651
--- Comment #1 from Quentin Barnes <qbarnes@gmail.com> 2013-03-25 20:59:31 ---
I have a small mistake in the above report. The problem does not reproduce on
RHEL6.2 (or earlier RHEL6 releases). Only on RHEL6.3 and later.
So it looks like the bug came in between: v3.1 and v3.2, RHEL5.7 and RHEL5.8,
and RHEL6.2 and RHEL6.3.
I'm still poking about to see if I can figure out which patch that is so I can
better have a guess at which subsystem.
--
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:[~2013-03-25 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 1:19 [Bug 55651] New: Non-atomic short write problem with O_APPEND bugzilla-daemon
2013-03-25 20:59 ` bugzilla-daemon [this message]
2013-03-27 18:40 ` [Bug 55651] " bugzilla-daemon
2013-03-27 18:46 ` bugzilla-daemon
2013-03-27 18:57 ` 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=20130325205931.D140F11FB35@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).