From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Benjamin LaHaise <bcrl@linux.intel.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [AIO] aio-2.6.13-rc6-B1
Date: Tue, 20 Sep 2005 12:23:10 +0200 [thread overview]
Message-ID: <1127211790.2051.9.camel@frecb000686> (raw)
In-Reply-To: <20050817184406.GA24961@linux.intel.com>
On Wed, 2005-08-17 at 14:44 -0400, Benjamin LaHaise wrote:
> The bugfix followup to the last aio rollup is now available at:
>
> http://www.kvack.org/~bcrl/patches/aio-2.6.13-rc6-B1-all.diff
>
> with the split up in:
>
> http://www.kvack.org/~bcrl/patches/aio-2.6.13-rc6-B1/
>
> This fixes the bugs noticed in the -B0 variant. Major changes in this
> patchset are:
>
> - added aio semaphore ops
> - aio thread based fallbacks
> - vectored aio file_operations
> - aio sendmsg/recvmsg via thread fallbacks
> - retry based aio pipe operations
>
> Comments?
>
> -ben
>
Hi Ben,
what's the point of calling wake_up_locked(&sem->wait) in
aio_down_wait? We're already in a wakeup path and end up
calling __wake_up_common recursively.
I think it may be one of the cause of my kernel hanging at the
very beginning.
When I remove this call things go further but at some point a
semaphore wait queue gets thrashed and __wake_up_common tries to
call an invalid callback function.
Any input appreciated.
Sébastien.
--
------------------------------------------------------
Sébastien Dugué BULL/FREC:B1-247
phone: (+33) 476 29 77 70 Bullcom: 229-7770
mailto:sebastien.dugue@bull.net
Linux POSIX AIO: http://www.bullopensource.org/posix
------------------------------------------------------
next prev parent reply other threads:[~2005-09-20 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 18:44 Benjamin LaHaise
2005-08-18 10:02 ` Suparna Bhattacharya
2005-08-17 23:16 ` Benjamin LaHaise
2005-08-18 16:22 ` Suparna Bhattacharya
2005-09-20 10:23 ` Sébastien Dugué [this message]
2005-09-20 19:13 ` Benjamin LaHaise
2005-09-21 11:33 ` Sébastien Dugué
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=1127211790.2051.9.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=bcrl@linux.intel.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®