All of lore.kernel.org
 help / color / mirror / Atom feed
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:46:35 +0000 (UTC)	[thread overview]
Message-ID: <20130327184635.A07D811FB3C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55651-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=55651


Quentin Barnes <qbarnes@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|ext4                        |VFS
     Kernel Version|3.8.4                       |3.9-rc4




--- Comment #3 from Quentin Barnes <qbarnes@gmail.com>  2013-03-27 18:46:35 ---
I tracked the problem down to the specific patch a50527b1.

Since now I know the problem is not specific to ext[34], I'm
updating the ticket to be the VFS layer.  (HOWEVER, Bugzilla
won't let me change the assignee to fs_vfs@kernel-bugs.osdl.org.
Can someone do that for me?)

With the patch in place (even up to and including 3.9-rc4), the
attached test (mlt-auto.c) fails.

If I git revert a50527b1 out of 3.9-rc4, the test passes.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-03-27 18:46 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 [this message]
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=20130327184635.A07D811FB3C@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 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.