From: Jan Stancek <jstancek@redhat.com>
To: Yan Lei <yanl.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fix race at exit by checking if write completed
Date: Tue, 5 Feb 2013 05:52:03 -0500 (EST) [thread overview]
Message-ID: <1211467206.206361.1360061523796.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1360049585-6091-1-git-send-email-yanl.fnst@cn.fujitsu.com>
----- Original Message -----
> From: "Yan Lei" <yanl.fnst@cn.fujitsu.com>
> To: ltp-list@lists.sourceforge.net
> Cc: "Yan Lei" <yanl.fnst@cn.fujitsu.com>
> Sent: Tuesday, 5 February, 2013 8:33:05 AM
> Subject: [LTP] [PATCH] fix race at exit by checking if write completed
>
> The same issue as:
> commit 352358cd9f69f6e8296cc201b14bae938287796e
> Author: Jan Stancek <jstancek@redhat.com>
> Date: Mon, 28 Jan 2013 11:36:48 +0100
> aio_fsync/2-1.c: fix race at exit, check if write completed
> This patch waits for aio_fsync to complete and after that
> checks that previously queued write is also completed.
>
> Signed-off-by: Yan Lei <yanl.fnst@cn.fujitsu.com>
I wonder why I missed that. Definitely same issue as in 2-1.
Acked-by: Jan Stancek <jstancek@redhat.com>
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-02-05 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 7:33 [LTP] [PATCH] fix race at exit by checking if write completed Yan Lei
2013-02-05 10:52 ` Jan Stancek [this message]
2013-02-05 12:02 ` chrubis
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=1211467206.206361.1360061523796.JavaMail.root@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanl.fnst@cn.fujitsu.com \
/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