All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20181217181148.GA3341@redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index a85485b..219d63b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -99,7 +99,7 @@ page_mkclean and force a page_mkwrite once write back ends. This is
 the situation we are inheriting (and i am personnaly not happy with
 that).
 
->From my point of view we are left with 2 choices:
+From my point of view we are left with 2 choices:
     [C1] break all drivers that do not abide by the page_mkclean and
          page_mkwrite
     [C2] mitigate as much as possible the issue
@@ -169,7 +169,7 @@ in some way disabling page cleaning ie we still write back content so
 that data loss is still unlikely but pages stays dirty and it disables
 anything that rely on page_mkwrite including COW.
 
->From fs point of view it is as if page is frozen in being dirty and
+From fs point of view it is as if page is frozen in being dirty and
 under write for undefined period of time. We only mitigate the data
 loss by allowing write to happen using a bounce page (so that layer
 down the stack get a page with stable content ie a snapshot).
@@ -191,4 +191,4 @@ DIO being software i believe it can be told to understand this special
 case.
 
 Cheers,
-J�r�me
+Jérôme
diff --git a/a/content_digest b/N1/content_digest
index 0d7b67b..6d0a7a5 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -136,7 +136,7 @@
  "the situation we are inheriting (and i am personnaly not happy with\n"
  "that).\n"
  "\n"
- ">From my point of view we are left with 2 choices:\n"
+ "From my point of view we are left with 2 choices:\n"
  "    [C1] break all drivers that do not abide by the page_mkclean and\n"
  "         page_mkwrite\n"
  "    [C2] mitigate as much as possible the issue\n"
@@ -206,7 +206,7 @@
  "that data loss is still unlikely but pages stays dirty and it disables\n"
  "anything that rely on page_mkwrite including COW.\n"
  "\n"
- ">From fs point of view it is as if page is frozen in being dirty and\n"
+ "From fs point of view it is as if page is frozen in being dirty and\n"
  "under write for undefined period of time. We only mitigate the data\n"
  "loss by allowing write to happen using a bounce page (so that layer\n"
  "down the stack get a page with stable content ie a snapshot).\n"
@@ -228,6 +228,6 @@
  "case.\n"
  "\n"
  "Cheers,\n"
- "J\303\257\302\277\302\275r\303\257\302\277\302\275me"
+ "J\303\251r\303\264me"
 
-fd97139f24b6725f4b9a5a592886495feba77d179b8a9e453581612c2faab0cc
+8a98d00f29d793a211036b97d52b2adfeb1e44fea33ed32d8100ac4fb64f85a3

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.