From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com, linux-aio@kvack.org,
mfasheh@suse.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, joe.jin@oracle.com
Subject: [Ocfs2-devel] [V4]fix ocfs2 aio/dio writing process hang
Date: Thu, 28 Jun 2012 16:48:03 +0800 [thread overview]
Message-ID: <4FEC1A43.7060309@oracle.com> (raw)
In-Reply-To: <20120628083454.GF18502@dhcp-172-17-9-228.mtv.corp.google.com>
On 06/28/2012 04:34 PM, Joel Becker wrote:
> Btw, do you want me to pull these through the ocfs2 tree, or are you
> sending them along yourself?
Please help pull these, great thanks.
>
> Joel
>
> On Wed, Jun 27, 2012 at 05:09:53PM +0800, Junxiao Bi wrote:
>> V4 changes:
>> add Acked-by: Joel Becker <jlbec@evilplan.org>
>>
>> V3 changes:
>> - add Cc: stable at vger.kernel.org in the patch header to align with stable rules
>> - add Acked-by: Jeff Moyer <jmoyer@redhat.com>
>>
>> V2 changes:
>> - update the patch header of the first patch to make it more clear.
>>
>>
>> This patch list fixes an issue about ocfs2 aio/dio write process hang.
>> The call trace is like this:
>> @ cat /proc/15913/stack
>> @ [<ffffffffa06e1085>] ocfs2_aiodio_wait+0x85/0xc0 [ocfs2]
>> @ [<ffffffffa06e3e39>] ocfs2_file_aio_write+0x99/0xa0 [ocfs2]
>> @ [<ffffffff811ace97>] aio_rw_vect_retry+0x87/0x150
>> @ [<ffffffff811aebd1>] aio_run_iocb+0x71/0x170
>> @ [<ffffffff811af59b>] io_submit_one+0x1ab/0x280
>> @ [<ffffffff811af77c>] do_io_submit+0x10c/0x1c0
>> @ [<ffffffff811af840>] sys_io_submit+0x10/0x20
>> @ [<ffffffff81509b42>] system_call_fastpath+0x16/0x1b
>> @ [<ffffffffffffffff>] 0xffffffffffffffff
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo at vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com, linux-aio@kvack.org,
mfasheh@suse.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, joe.jin@oracle.com
Subject: Re: [V4]fix ocfs2 aio/dio writing process hang
Date: Thu, 28 Jun 2012 16:48:03 +0800 [thread overview]
Message-ID: <4FEC1A43.7060309@oracle.com> (raw)
In-Reply-To: <20120628083454.GF18502@dhcp-172-17-9-228.mtv.corp.google.com>
On 06/28/2012 04:34 PM, Joel Becker wrote:
> Btw, do you want me to pull these through the ocfs2 tree, or are you
> sending them along yourself?
Please help pull these, great thanks.
>
> Joel
>
> On Wed, Jun 27, 2012 at 05:09:53PM +0800, Junxiao Bi wrote:
>> V4 changes:
>> add Acked-by: Joel Becker <jlbec@evilplan.org>
>>
>> V3 changes:
>> - add Cc: stable@vger.kernel.org in the patch header to align with stable rules
>> - add Acked-by: Jeff Moyer <jmoyer@redhat.com>
>>
>> V2 changes:
>> - update the patch header of the first patch to make it more clear.
>>
>>
>> This patch list fixes an issue about ocfs2 aio/dio write process hang.
>> The call trace is like this:
>> @ cat /proc/15913/stack
>> @ [<ffffffffa06e1085>] ocfs2_aiodio_wait+0x85/0xc0 [ocfs2]
>> @ [<ffffffffa06e3e39>] ocfs2_file_aio_write+0x99/0xa0 [ocfs2]
>> @ [<ffffffff811ace97>] aio_rw_vect_retry+0x87/0x150
>> @ [<ffffffff811aebd1>] aio_run_iocb+0x71/0x170
>> @ [<ffffffff811af59b>] io_submit_one+0x1ab/0x280
>> @ [<ffffffff811af77c>] do_io_submit+0x10c/0x1c0
>> @ [<ffffffff811af840>] sys_io_submit+0x10/0x20
>> @ [<ffffffff81509b42>] system_call_fastpath+0x16/0x1b
>> @ [<ffffffffffffffff>] 0xffffffffffffffff
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-06-28 8:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 9:09 [Ocfs2-devel] [V4]fix ocfs2 aio/dio writing process hang Junxiao Bi
2012-06-27 9:09 ` Junxiao Bi
2012-06-27 9:09 ` [Ocfs2-devel] [PATCH v4 1/2] aio: make kiocb->private NUll in init_sync_kiocb() Junxiao Bi
2012-06-27 9:09 ` Junxiao Bi
2012-06-28 22:39 ` [Ocfs2-devel] " Andrew Morton
2012-06-28 22:39 ` Andrew Morton
2012-06-29 9:22 ` [Ocfs2-devel] " Joel Becker
2012-06-29 9:22 ` Joel Becker
2012-06-29 10:17 ` [Ocfs2-devel] " Junxiao Bi
2012-06-29 10:17 ` Junxiao Bi
2012-06-29 10:29 ` [Ocfs2-devel] " Andrew Morton
2012-06-29 10:29 ` Andrew Morton
2012-06-29 10:48 ` [Ocfs2-devel] " Junxiao Bi
2012-06-29 10:48 ` Junxiao Bi
2012-06-29 10:49 ` [Ocfs2-devel] " Junxiao Bi
2012-06-29 10:49 ` Junxiao Bi
2012-07-04 6:13 ` [Ocfs2-devel] " Joel Becker
2012-07-04 6:13 ` Joel Becker
2012-06-27 9:09 ` [Ocfs2-devel] [PATCH v4 2/2] ocfs2: clear unaligned io flag when dio fails Junxiao Bi
2012-06-27 9:09 ` Junxiao Bi
2012-07-04 7:34 ` [Ocfs2-devel] " Joel Becker
2012-07-04 7:34 ` Joel Becker
2012-07-04 7:51 ` Junxiao Bi
2012-07-04 7:51 ` Junxiao Bi
2012-07-05 9:22 ` Joel Becker
2012-07-05 9:22 ` Joel Becker
2012-06-28 8:34 ` [V4]fix ocfs2 aio/dio writing process hang Joel Becker
2012-06-28 8:48 ` Junxiao Bi [this message]
2012-06-28 8:48 ` Junxiao Bi
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=4FEC1A43.7060309@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=joe.jin@oracle.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.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 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.