From: Andrew Morton <akpm@osdl.org>
To: suparna@in.ibm.com
Cc: sebastien.dugue@bull.net, linux-aio@kvack.org,
linux-kernel@vger.kernel.org, pbadari@us.ibm.com,
daniel@osdl.org
Subject: Re: [PATCH] 2.6.10 - direct-io async short read bug
Date: Tue, 8 Mar 2005 01:41:41 -0800 [thread overview]
Message-ID: <20050308014141.08a546a9.akpm@osdl.org> (raw)
In-Reply-To: <20050308094159.GA4144@in.ibm.com>
Suparna Bhattacharya <suparna@in.ibm.com> wrote:
>
> > > can you spot what is going wrong here that we have to try and
> > > workaround this later ?
> >
> > Good question. Do we have the i_sem coverage to prevent a concurrent
> > truncate?
> >
> > But from Sebastien's description it doesn't soound as if a concurrent
> > truncate is involved.
>
> Daniel McNeil has a testcase that reproduces the problem - seemed
> like a single thread thing - that's what puzzles me.
OK. It'd be nice if we could find a solution which gets around that i_size
access in the ISR, if someone has the time to look into it?
next prev parent reply other threads:[~2005-03-08 9:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 10:00 [PATCH] 2.6.10 - direct-io async short read bug Sébastien Dugué
2005-03-08 6:39 ` Andrew Morton
2005-03-08 9:09 ` Suparna Bhattacharya
2005-03-08 9:18 ` Andrew Morton
2005-03-08 9:41 ` Suparna Bhattacharya
2005-03-08 9:41 ` Andrew Morton [this message]
2005-03-08 10:27 ` Suparna Bhattacharya
2005-03-08 10:27 ` Andrew Morton
2005-03-08 17:23 ` Badari Pulavarty
2005-03-08 19:18 ` Badari Pulavarty
2005-03-08 23:27 ` Daniel McNeil
2005-03-08 23:54 ` Badari Pulavarty
2005-03-09 4:07 ` Joel Becker
2005-03-09 9:50 ` Sébastien Dugué
2005-03-09 15:20 ` Suparna Bhattacharya
2005-03-09 19:53 ` Andrew Morton
2005-03-09 21:18 ` Joel Becker
2005-03-09 21:31 ` Badari Pulavarty
2005-03-09 22:39 ` Andrew Morton
2005-03-09 22:45 ` Badari Pulavarty
2005-03-09 1:44 ` Daniel McNeil
2005-03-09 15:58 ` Badari Pulavarty
-- strict thread matches above, loose matches on Subject: below --
2005-03-08 9:46 Sébastien Dugué
2005-03-08 10:16 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=20050308014141.08a546a9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=daniel@osdl.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=sebastien.dugue@bull.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox