From: Andrew Morton <akpm@digeo.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nsharoff@us.ibm.com, Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: 2.5.70-mm2
Date: Fri, 30 May 2003 04:17:04 -0700 [thread overview]
Message-ID: <20030530041704.5d740ee2.akpm@digeo.com> (raw)
In-Reply-To: <200305291452.09041.pbadari@us.ibm.com>
Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> 2.5.70-mm2 seems to hang while running LTP.
It is actually a VFS bug. A brand new one. Here's a fix, but we should
check that it still gets all the LTP writev cases right.
A couple of ext3 bugs in -mm2 have been fixed so please don't spend time
stresstesting it until mm3.
Thanks.
The recent writev() fix broke the invariant that ->commit_write _must_ be
called after a successful ->prepare_write(). It leaves ext3 with a
transaction stuck open and the filesystem locks up.
mm/filemap.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff -puN mm/filemap.c~generic_file_write-commit_write-fix mm/filemap.c
--- 25/mm/filemap.c~generic_file_write-commit_write-fix 2003-05-30 04:01:19.000000000 -0700
+++ 25-akpm/mm/filemap.c 2003-05-30 04:04:11.000000000 -0700
@@ -1718,10 +1718,9 @@ generic_file_aio_write_nolock(struct kio
copied = filemap_copy_from_user_iovec(page, offset,
cur_iov, iov_base, bytes);
flush_dcache_page(page);
+ status = a_ops->commit_write(file, page, offset,
+ offset + copied);
if (likely(copied > 0)) {
- status = a_ops->commit_write(file, page, offset,
- offset + copied);
-
if (!status)
status = copied;
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-30 11:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 8:29 2.5.70-mm2 Andrew Morton
2003-05-29 8:49 ` 2.5.70-mm2 Andrew Morton
2003-05-29 11:23 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:05 ` 2.5.70-mm2 John Stoffel
2003-05-30 20:30 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:56 ` 2.5.70-mm2 John Stoffel
2003-05-30 22:36 ` 2.5.70-mm2 Mingming Cao
2003-05-29 12:55 ` 2.5.70-mm2 still dies with RAID-1 Helge Hafting
2003-05-29 21:52 ` 2.5.70-mm2 Badari Pulavarty
2003-05-30 11:17 ` Andrew Morton [this message]
2003-05-29 16:48 2.5.70-mm2 Downing, Thomas
2003-05-29 17:36 ` 2.5.70-mm2 Andrew Morton
2003-05-29 21:22 ` 2.5.70-mm2 John Stoffel
2003-05-29 21:35 ` 2.5.70-mm2 Andrew Morton
2003-05-29 20:08 ` 2.5.70-mm2 Paul Larson
2003-05-29 19:08 2.5.70-mm2 Downing, Thomas
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=20030530041704.5d740ee2.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nsharoff@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=schwidefsky@de.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