From: Andrew Morton <akpm@zip.com.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20pre5aa1
Date: Wed, 04 Sep 2002 16:56:09 -0700 [thread overview]
Message-ID: <3D769D99.CF054558@zip.com.au> (raw)
In-Reply-To: <20020904233528.GA1238@dualathlon.random>
Andrea Arcangeli wrote:
>
> ...
>
> The 2.5 libaio that works with this kernel and 2.5 is here:
>
> http://www.us.kernel.org/pub/linux/kernel/people/andrea/libaio/libaio-0.3.15-2.5.tar.gz
Thanks for doing this. The lack of AIO-aware applications and of
testing tools for AIO is a bit of a worry at present.
> Only in 2.4.20pre5aa1: 00_prepare-write-fixes-3-1
>
> Also check the i_size is in sync with the last block we allocated in
> the metadata, it won't be updated in the commit_write if prepare_write
> is failing.
That's the right thing to do I guess. Is this a problem in practice?
If prepare_write() fails, generic_file_write() will truncate back to
the current i_size?
> Only in 2.4.20pre5aa1: 9920_kgdb-1.gz
>
> kgdb from akpm.
Life in the fast lane ;) Kudos to Amit Kale.
next prev parent reply other threads:[~2002-09-04 23:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 23:35 2.4.20pre5aa1 Andrea Arcangeli
2002-09-04 23:56 ` Andrew Morton [this message]
2002-09-05 0:25 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 12:44 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 16:53 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 17:09 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:41 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 18:46 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:59 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:02 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:13 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:17 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:48 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:06 ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:15 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:26 ` 2.4.20pre5aa1 Christoph Hellwig
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=3D769D99.CF054558@zip.com.au \
--to=akpm@zip.com.au \
--cc=andrea@suse.de \
--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®