From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: akpm@osdl.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH] s390: lost dirty bits.
Date: Tue, 15 Jun 2004 19:44:36 +0200 [thread overview]
Message-ID: <20040615174436.GA10098@mschwid3.boeblingen.de.ibm.com> (raw)
Hi Andrew,
we just tracked down a severe bug in the memory management
code of s390. There is a race window where s390 can loose
a dirty bit. I never expected that SetPageUptodate is called
on an already up to date page...
blue skies,
Martin.
---
[PATCH] s390: lost dirty bits.
The SetPageUptodate function is called for pages that are already
up to date. The arch_set_page_uptodate function of s390 may not
clear the dirty bit in that case otherwise a dirty bit which is set
between the start of an i/o for a writeback and a following call
to SetPageUptodate is lost.
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
diffstat:
--- linux-2.5/include/asm-s390/pgtable.h 24 Mar 2004 18:18:22 -0000 1.23
+++ linux-2.5/include/asm-s390/pgtable.h 15 Jun 2004 16:43:35 -0000 1.23.2.1
@@ -652,7 +652,8 @@
#define arch_set_page_uptodate(__page) \
do { \
- asm volatile ("sske %0,%1" : : "d" (0), \
+ if (!PageUptodate(__page)) \
+ asm volatile ("sske %0,%1" : : "d" (0), \
"a" (__pa((__page-mem_map) << PAGE_SHIFT)));\
} while (0)
--
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 reply other threads:[~2004-06-15 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 17:44 Martin Schwidefsky [this message]
2004-06-16 4:09 ` Andrew Morton
2004-06-16 7:12 ` Christoph Hellwig
2004-06-16 8:42 Martin Schwidefsky
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=20040615174436.GA10098@mschwid3.boeblingen.de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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