From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 55651] Non-atomic short write problem with O_APPEND
Date: Wed, 27 Mar 2013 18:57:25 +0000 (UTC) [thread overview]
Message-ID: <20130327185725.313AA11FB3C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55651-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=55651
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |tytso@mit.edu
AssignedTo|fs_ext4@kernel-bugs.osdl.or |jack@suse.cz
|g |
--- Comment #4 from Theodore Tso <tytso@mit.edu> 2013-03-27 18:57:24 ---
The commit in question (a50527b1) was authored by Jan Kara so I've changed the
assignee of this bug to him.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2013-03-27 18:57 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 ` [Bug 55651] " bugzilla-daemon
2013-03-27 18:40 ` bugzilla-daemon
2013-03-27 18:46 ` bugzilla-daemon
2013-03-27 18:57 ` bugzilla-daemon [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=20130327185725.313AA11FB3C@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).