From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test6-mm4 - oops in __aio_run_iocbs()
Date: 9 Oct 2003 19:24:45 GMT [thread overview]
Message-ID: <bm4clt$5n6$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20031009111624.GA11549@in.ibm.com
In article <20031009111624.GA11549@in.ibm.com>,
Suparna Bhattacharya <suparna@in.ibm.com> wrote:
| On Wed, Oct 08, 2003 at 04:18:15PM -0700, Daniel McNeil wrote:
|
| __aio_run_iocbs should have been called only for buffered i/o,
| so this sounds like an O_DIRECT fallback to buffered i/o.
| Possibly after already submitting some blocks direct to BIO,
| the i/o completion path for which ends up calling aio_complete
| releasing the iocb. That could explain the use-after-free situation
| you see.
|
| But, O_DIRECT write should fallback to buffered i/o only if it
| encounters holes in the middle of the file, not for simple appends
| as in your case. Need to figure out how this could have happened ...
Are the write kept ordered?
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-10-09 19:34 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
2003-10-09 19:24 ` bill davidsen [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='bm4clt$5n6$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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 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.