From: Yongzhi Pan <panyongzhi@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
"Theodore T'so" <tytso@mit.edu>, Christoph Hellwig <hch@lst.de>,
Chris Mason <clm@fb.com>, Dave Chinner <david@fromorbit.com>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"J. Bruce Fields" <bfields@citi.umich.edu>
Subject: Re: Update of file offset on write() etc. is non-atomic with I/O
Date: Fri, 7 Mar 2014 11:38:14 +0800 [thread overview]
Message-ID: <CACu+fTYSsmAMiV8w=BzYLEbf2WtiRO78=cy_G+1e5sk0p46vKg@mail.gmail.com> (raw)
In-Reply-To: <53188E50.70808@gmail.com>
2014-03-06 23:03 GMT+08:00 Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>:
>
> The original code (where Yongzhi Pan reported an issue) and
> the multi_writer.c test code where both mine actually. Anyway,
> I applied the patch to 3.14-rc5, and I (not withstanding the other
> points raised by Al about the patch) I confirm that this patch makes
> the problem that I'm seeing go away.
>
> Thanks for looking at this, Linus.
>
> Cheers,
>
> Michael
I tested the original patch on 3.13.5, the multi_writer.c test code
and the code in your book both run flawlessly.
Best Regards,
Yongzhi Pan
next prev parent reply other threads:[~2014-03-07 3:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:41 Update of file offset on write() etc. is non-atomic with I/O Michael Kerrisk (man-pages)
2014-02-18 13:00 ` Michael Kerrisk
2014-02-20 17:14 ` Linus Torvalds
2014-03-03 17:36 ` Linus Torvalds
2014-03-03 21:45 ` Al Viro
2014-03-03 21:56 ` Linus Torvalds
2014-03-03 22:09 ` Al Viro
2014-03-03 22:20 ` Linus Torvalds
2014-03-03 22:01 ` Linus Torvalds
2014-03-03 22:10 ` Al Viro
2014-03-03 22:22 ` Linus Torvalds
2014-03-06 15:03 ` Michael Kerrisk (man-pages)
2014-03-07 3:38 ` Yongzhi Pan [this message]
[not found] <a8df285f-de7f-4a3a-9a19-e0ad07ab3a5c@blur>
2014-02-20 18:15 ` Zuckerman, Boris
2014-02-20 18:29 ` Al Viro
2014-02-21 6:01 ` Michael Kerrisk (man-pages)
2014-02-23 1:18 ` Kevin Easton
2014-02-23 7:38 ` Michael Kerrisk (man-pages)
2014-03-03 21:03 George Spelvin
2014-03-03 21:26 ` Al Viro
2014-03-03 21:52 ` Linus Torvalds
2014-03-03 22:01 ` Al Viro
2014-03-03 22:17 ` Linus Torvalds
2014-03-03 23:28 ` Al Viro
2014-03-03 23:34 ` Linus Torvalds
2014-03-03 23:42 ` Al Viro
2014-03-03 23:59 ` Linus Torvalds
2014-03-04 0:23 ` Al Viro
2014-03-04 0:42 ` Linus Torvalds
2014-03-04 1:05 ` Al Viro
2014-03-04 20:00 ` Al Viro
2014-03-04 21:17 ` Linus Torvalds
2014-03-05 0:04 ` Al Viro
2014-03-10 15:55 ` Al Viro
2014-03-03 22:55 ` Linus Torvalds
2014-03-03 23:23 ` Linus Torvalds
2014-03-03 23:39 ` Al Viro
2014-03-03 23:54 ` Linus Torvalds
2014-03-03 23:54 ` Al Viro
2014-03-04 20:11 ` Cedric Blancher
2014-03-04 0:07 ` George Spelvin
2014-05-04 7:04 ` Michael Kerrisk
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='CACu+fTYSsmAMiV8w=BzYLEbf2WtiRO78=cy_G+1e5sk0p46vKg@mail.gmail.com' \
--to=panyongzhi@gmail.com \
--cc=bfields@citi.umich.edu \
--cc=clm@fb.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).