All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel McNeil <daniel@osdl.org>
To: Suparna Bhattacharya <suparna@in.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-aio@kvack.org" <linux-aio@kvack.org>
Subject: Re: 2.6.0-test6-mm4 - oops in __aio_run_iocbs()
Date: 10 Oct 2003 15:11:38 -0700	[thread overview]
Message-ID: <1065823898.1839.21.camel@ibm-c.pdx.osdl.net> (raw)
In-Reply-To: <20031010114821.GA4357@in.ibm.com>

On Fri, 2003-10-10 at 04:48, Suparna Bhattacharya wrote:

> Could you try applying the following hack and see if it makes a 
> difference ?
> 
> I was able to recreate an oops running aiocp with the same arguments
> that you mentioned on 2.6.0-test6-mm4; and that didn't seem to
> occur when I applied this patch.
> 
> Note: This is not a complete fix though and probably room for doing this 
> in a cleaner way. If what I suspect is going on, we'll need more work to get 
> there - like thinking through the case where a request spans an allocated
> region followed by a hole.
> 
> Regards
> Suparna

good news, I tried the patch and the oops no longer occurs.

I also added code to aiocp to check if the AIO reads are completing out
of order, which would cause the AIO writes to out of order.  The reads
are completing in order.  However, I added code to check if the AIO
writes are completing out of order, and, if fact, they do.  Not very
often, but I got 8 i/o where an i/o farther in file completes before
an earlier i/o.

Daniel


  reply	other threads:[~2003-10-10 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05  8:33 2.6.0-test6-mm4 Andrew Morton
2003-10-05  8:33 ` 2.6.0-test6-mm4 Andrew Morton
2003-10-05  9:26 ` 2.6.0-test6-mm4 Daniele Bellucci
2003-10-05  9:26   ` 2.6.0-test6-mm4 Daniele Bellucci
2003-10-08 23:18 ` 2.6.0-test6-mm4 - oops in __aio_run_iocbs() Daniel McNeil
2003-10-09 11:16   ` Suparna Bhattacharya
2003-10-09 12:59     ` Suparna Bhattacharya
2003-10-09 17:42       ` Daniel McNeil
2003-10-09 17:38     ` Daniel McNeil
2003-10-10  8:34       ` Suparna Bhattacharya
2003-10-10 11:48         ` Suparna Bhattacharya
2003-10-10 22:11           ` Daniel McNeil [this message]
2003-10-09 19:24     ` bill davidsen

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=1065823898.1839.21.camel@ibm-c.pdx.osdl.net \
    --to=daniel@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suparna@in.ibm.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.