All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20090608123133.GA7944@localhost>

diff --git a/a/1.txt b/N1/1.txt
index 6a946f7..b3ddb2d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -42,7 +42,7 @@ its own IO.
 > >
 > >> that is the semantics of a writer waiting to get the lock while it's
 > >> acquired by
-> >> some reader:The caller(e.g. truncate_inode_pages_range()  and
+> >> some reader:The caller(e.g. truncate_inode_pages_range() A and
 > >> invalidate_inode_pages2_range()) are the writers waiting for
 > >> writeback readers (as you clarified ) to finish their job, right ?
 > >
@@ -140,7 +140,7 @@ Fengguang
 > > Thanks,
 > > Fengguang
 > >
-> >> > The writeback bit is _widely_ used.  test_set_page_writeback() is
+> >> > The writeback bit is _widely_ used. A test_set_page_writeback() is
 > >> > directly used by NFS/AFS etc. But its main user is in fact
 > >> > set_page_writeback(), which is called in 26 places.
 > >> >
@@ -156,8 +156,8 @@ Fengguang
 > >> >
 > >> > The reason truncate_inode_pages_range() has to wait on writeback page
 > >> > is to ensure data integrity. Otherwise if there comes two events:
-> >> >        truncate page A at offset X
-> >> >        populate page B at offset X
+> >> > A  A  A  A truncate page A at offset X
+> >> > A  A  A  A populate page B at offset X
 > >> > If A and B are all writeback pages, then B can hit disk first and then
 > >> > be overwritten by A. Which corrupts the data at offset X from user's POV.
 > >> >
@@ -173,7 +173,13 @@ Fengguang
 > >> > --
 > >> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
 > >> > the body of a message to majordomo@vger.kernel.org
-> >> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
-> >> > Please read the FAQ at  http://www.tux.org/lkml/
+> >> > More majordomo info at A http://vger.kernel.org/majordomo-info.html
+> >> > Please read the FAQ at A http://www.tux.org/lkml/
 > >> >
 > >
+
+--
+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:"dont@kvack.org"> email@kvack.org </a>
diff --git a/a/content_digest b/N1/content_digest
index 4f564ce..e086d86 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -66,7 +66,7 @@
  "> >\n"
  "> >> that is the semantics of a writer waiting to get the lock while it's\n"
  "> >> acquired by\n"
- "> >> some reader:The caller(e.g. truncate_inode_pages_range() \302\240and\n"
+ "> >> some reader:The caller(e.g. truncate_inode_pages_range() A and\n"
  "> >> invalidate_inode_pages2_range()) are the writers waiting for\n"
  "> >> writeback readers (as you clarified ) to finish their job, right ?\n"
  "> >\n"
@@ -164,7 +164,7 @@
  "> > Thanks,\n"
  "> > Fengguang\n"
  "> >\n"
- "> >> > The writeback bit is _widely_ used. \302\240test_set_page_writeback() is\n"
+ "> >> > The writeback bit is _widely_ used. A test_set_page_writeback() is\n"
  "> >> > directly used by NFS/AFS etc. But its main user is in fact\n"
  "> >> > set_page_writeback(), which is called in 26 places.\n"
  "> >> >\n"
@@ -180,8 +180,8 @@
  "> >> >\n"
  "> >> > The reason truncate_inode_pages_range() has to wait on writeback page\n"
  "> >> > is to ensure data integrity. Otherwise if there comes two events:\n"
- "> >> > \302\240 \302\240 \302\240 \302\240truncate page A at offset X\n"
- "> >> > \302\240 \302\240 \302\240 \302\240populate page B at offset X\n"
+ "> >> > A  A  A  A truncate page A at offset X\n"
+ "> >> > A  A  A  A populate page B at offset X\n"
  "> >> > If A and B are all writeback pages, then B can hit disk first and then\n"
  "> >> > be overwritten by A. Which corrupts the data at offset X from user's POV.\n"
  "> >> >\n"
@@ -197,9 +197,15 @@
  "> >> > --\n"
  "> >> > To unsubscribe from this list: send the line \"unsubscribe linux-kernel\" in\n"
  "> >> > the body of a message to majordomo@vger.kernel.org\n"
- "> >> > More majordomo info at \302\240http://vger.kernel.org/majordomo-info.html\n"
- "> >> > Please read the FAQ at \302\240http://www.tux.org/lkml/\n"
+ "> >> > More majordomo info at A http://vger.kernel.org/majordomo-info.html\n"
+ "> >> > Please read the FAQ at A http://www.tux.org/lkml/\n"
  "> >> >\n"
- > >
+ "> >\n"
+ "\n"
+ "--\n"
+ "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
+ "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
+ "see: http://www.linux-mm.org/ .\n"
+ "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>"
 
-8b1cbf10b64e4c124bfcfda8fb76fd2df620e7baf7400d21031bd619cccfef5a
+ee09acf60b1adb5dc9e81c72c06e2149b76c495ec6499a7a26f8e343cfc5566c

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.