All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] aio_fsync: wait until aio_fsync completes
Date: Wed, 21 Aug 2013 14:35:52 +0800	[thread overview]
Message-ID: <52145FC8.2040207@cn.fujitsu.com> (raw)
In-Reply-To: <a4b10219d9304cc8ea0fb62447640710d72d05c6.1376300996.git.jstancek@redhat.com>

On 08/12/2013 07:03 PM, Jan Stancek wrote:
> This patch introduces wait so that testcases exit doesn't race
> with completion of aio_fsync.
> 
> This is to avoid SIGSEGV:
>  #0  0x000003fffd1f4a24 in _IO_flush_all_lockp () at genops.c:850
>  #1  0x000003fffd1f4b8e in _IO_cleanup () at genops.c:1010
>  #2  0x000003fffd1a88f6 in __run_exit_handlers () at exit.c:90
>  #3  0x000003fffd1a89b0 in __GI_exit () at exit.c:99
>  #4  0x000003fffd18c822 in __libc_start_main () at libc-start.c:292
>  #5  0x0000000080000b76 in _start ()
> 
> Signed-off-by: Jan Stancek <jstancek@redhat.com>

I pushed this, thank you ;)

Wanlong Gao


------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2013-08-21  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 11:03 [LTP] [PATCH] aio_fsync: wait until aio_fsync completes Jan Stancek
2013-08-12 12:07 ` chrubis
2013-08-20  6:52 ` Wanlong Gao
2013-08-21  6:35 ` Wanlong Gao [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=52145FC8.2040207@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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.