diff for duplicates of <1520956602.10285.10.camel@synopsys.com>

diff --git a/a/1.txt b/N1/1.txt
index 1d59670..0bd67db 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,47 +1,47 @@
-On Tue, 2018-03-13 at 16:05 +0200, Adrian Hunter wrote:
+On Tue, 2018-03-13@16:05 +0200, Adrian Hunter wrote:
 > On 13/03/18 14:04, Evgeniy Didin wrote:
 > > Hello Adrian,
 > > 
 > > I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark
 > > runs with errors on arc/hsdk board. After bisecting between 4.15 and 4.16-rc1,
-> > I have found that errors started after 
+> > I have found that errors started after?
 > > commit 81196976ed94 (mmc: block: Add blk-mq support).
 > > 
 > > Error message is like:
 > > 
-> > > # bonnie++ -u root -r 256 -s 512 -x 1 -d  /mnt 
+> > > # bonnie++ -u root -r 256 -s 512 -x 1 -d??/mnt?
 > > > Using uid:0, gid:0.
 > > > Writing with putc()...random: crng init done
 > > > done
 > > > Writing intelligently...INFO: task kworker/u8:0:5 blocked for more than 10 seconds.
-> > >       Not tainted 4.15.0-rc3-00012-g81196976ed94-dirty #1
+> > > ??????Not tainted 4.15.0-rc3-00012-g81196976ed94-dirty #1
 > > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
-> > > kworker/u8:0    D    0     5      2 0x00000000
+> > > kworker/u8:0????D????0?????5??????2 0x00000000
 > > > Workqueue: writeback wb_workfn (flush-179:0)
 > > > 
 > > > Stack Trace:
-> > >   __switch_to+0x0/0xac
-> > >   __schedule+0x1b8/0x738
-> > >   io_schedule+0x5c/0xc0
-> > >   bit_wait_io+0xc/0x48
-> > >   out_of_line_wait_on_bit+0x78/0xc0
-> > >   do_get_write_access+0x1aa/0x4cc
-> > >   jbd2_journal_get_write_access+0x32/0x74
-> > >   __ext4_journal_get_write_access+0x3a/0xac
-> > >   ext4_mb_mark_diskspace_used+0x66/0x5b0
-> > >   ext4_mb_new_blocks+0x1ee/0x830
-> > >   ext4_ext_map_blocks+0x504/0xcac
-> > >   ext4_map_blocks+0x262/0x5e8
-> > >   mpage_map_and_submit_extent+0xb8/0x648
-> > >   ext4_writepages+0x5ce/0x6b4
-> > >   do_writepages+0x20/0x84
-> > >   __writeback_single_inode+0x2a/0x154
-> > >   wb_writeback+0x538/0xae0
-> > >   wb_workfn+0x17c/0x334
-> > >   process_one_work+0x1a6/0x350
-> > >   worker_thread+0xf2/0x478
-> > >   kthread+0x120/0x13c
-> > >   ret_from_fork+0x18/0x1c
+> > > ??__switch_to+0x0/0xac
+> > > ??__schedule+0x1b8/0x738
+> > > ??io_schedule+0x5c/0xc0
+> > > ??bit_wait_io+0xc/0x48
+> > > ??out_of_line_wait_on_bit+0x78/0xc0
+> > > ??do_get_write_access+0x1aa/0x4cc
+> > > ??jbd2_journal_get_write_access+0x32/0x74
+> > > ??__ext4_journal_get_write_access+0x3a/0xac
+> > > ??ext4_mb_mark_diskspace_used+0x66/0x5b0
+> > > ??ext4_mb_new_blocks+0x1ee/0x830
+> > > ??ext4_ext_map_blocks+0x504/0xcac
+> > > ??ext4_map_blocks+0x262/0x5e8
+> > > ??mpage_map_and_submit_extent+0xb8/0x648
+> > > ??ext4_writepages+0x5ce/0x6b4
+> > > ??do_writepages+0x20/0x84
+> > > ??__writeback_single_inode+0x2a/0x154
+> > > ??wb_writeback+0x538/0xae0
+> > > ??wb_workfn+0x17c/0x334
+> > > ??process_one_work+0x1a6/0x350
+> > > ??worker_thread+0xf2/0x478
+> > > ??kthread+0x120/0x13c
+> > > ??ret_from_fork+0x18/0x1c
 > > 
 > > There are some details of hsdk_defconfig presented bellow:
 > > 
@@ -58,7 +58,7 @@ On Tue, 2018-03-13 at 16:05 +0200, Adrian Hunter wrote:
 > > still it is strange, that some process is running in kernel space for a long time (at least 10sec).
 > > What is strange, before metioned commit I can't reproduce this behaviour.
 > > 
-> > I am wondering is this expected behaviour? 
+> > I am wondering is this expected behaviour??
 > 
 > Was the performance affected? i.e. the results from bonnie++
 I have run bonnie++ several times before and after mentioned commit. Here is output:
@@ -72,7 +72,7 @@ ARCLinux,512M,4453,36,6474,1,5852,0,12940,99,344329,100,+++++,+++,16,22168,98,++
 ARCLinux,512M,5159,42,6944,1,5658,0,12945,99,344290,100,+++++,+++,16,22295,100,+++++,+++,32715,99,22888,99,+++++,+++,32007,99
 ARCLinux,512M,5170,42,6840,2,5315,0,12946,99,343889,100,+++++,+++,16,22445,100,+++++,+++,32681,99,22967,100,+++++,+++,32117,99
 --------------------------------------------------<8------------------------------------------------------------------------
-              ^^^^ 
+              ^^^^?
 If i understand correctly, in third column is shown "sequential output" per character speed (K/sec), which decreased.
 
 > What mount options did you use?
@@ -81,7 +81,3 @@ I didn't use any options. Simply:
 
 Best regards,
 Evgeniy Didin
-_______________________________________________
-linux-snps-arc mailing list
-linux-snps-arc@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-snps-arc
diff --git a/a/content_digest b/N1/content_digest
index c1ef7b7..baf542b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,66 +1,55 @@
  "ref\01520942674.10285.8.camel@synopsys.com\0"
  "ref\0486fe92e-9b53-53a4-f98d-129a97032470@intel.com\0"
- "From\0Evgeniy Didin <Evgeniy.Didin@synopsys.com>\0"
- "Subject\0Re: mmc: block: bonnie++ runs with errors on arc/hsdk board\0"
+ "From\0Evgeniy.Didin@synopsys.com (Evgeniy Didin)\0"
+ "Subject\0mmc: block: bonnie++ runs with errors on arc/hsdk board\0"
  "Date\0Tue, 13 Mar 2018 15:56:42 +0000\0"
- "To\0adrian.hunter@intel.com <adrian.hunter@intel.com>"
- " Evgeniy.Didin@synopsys.com <Evgeniy.Didin@synopsys.com>\0"
- "Cc\0ulf.hansson@linaro.org <ulf.hansson@linaro.org>"
-  linux-ext4@vger.kernel.org <linux-ext4@vger.kernel.org>
-  tytso@mit.edu <tytso@mit.edu>
-  linus.walleij@linaro.org <linus.walleij@linaro.org>
-  Alexey.Brodkin@synopsys.com <Alexey.Brodkin@synopsys.com>
-  linux-mmc@vger.kernel.org <linux-mmc@vger.kernel.org>
-  jh80.chung@samsung.com <jh80.chung@samsung.com>
-  adilger.kernel@dilger.ca <adilger.kernel@dilger.ca>
-  linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org>
- " Eugeniy.Paltsev@synopsys.com <Eugeniy.Paltsev@synopsys.com>\0"
+ "To\0linux-snps-arc@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
- "On Tue, 2018-03-13 at 16:05 +0200, Adrian Hunter wrote:\n"
+ "On Tue, 2018-03-13@16:05 +0200, Adrian Hunter wrote:\n"
  "> On 13/03/18 14:04, Evgeniy Didin wrote:\n"
  "> > Hello Adrian,\n"
  "> > \n"
  "> > I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark\n"
  "> > runs with errors on arc/hsdk board. After bisecting between 4.15 and 4.16-rc1,\n"
- "> > I have found that errors started after\302\240\n"
+ "> > I have found that errors started after?\n"
  "> > commit 81196976ed94 (mmc: block: Add blk-mq support).\n"
  "> > \n"
  "> > Error message is like:\n"
  "> > \n"
- "> > > # bonnie++ -u root -r 256 -s 512 -x 1 -d\302\240\302\240/mnt\302\240\n"
+ "> > > # bonnie++ -u root -r 256 -s 512 -x 1 -d??/mnt?\n"
  "> > > Using uid:0, gid:0.\n"
  "> > > Writing with putc()...random: crng init done\n"
  "> > > done\n"
  "> > > Writing intelligently...INFO: task kworker/u8:0:5 blocked for more than 10 seconds.\n"
- "> > > \302\240\302\240\302\240\302\240\302\240\302\240Not tainted 4.15.0-rc3-00012-g81196976ed94-dirty #1\n"
+ "> > > ??????Not tainted 4.15.0-rc3-00012-g81196976ed94-dirty #1\n"
  "> > > \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n"
- "> > > kworker/u8:0\302\240\302\240\302\240\302\240D\302\240\302\240\302\240\302\2400\302\240\302\240\302\240\302\240\302\2405\302\240\302\240\302\240\302\240\302\240\302\2402 0x00000000\n"
+ "> > > kworker/u8:0????D????0?????5??????2 0x00000000\n"
  "> > > Workqueue: writeback wb_workfn (flush-179:0)\n"
  "> > > \n"
  "> > > Stack Trace:\n"
- "> > > \302\240\302\240__switch_to+0x0/0xac\n"
- "> > > \302\240\302\240__schedule+0x1b8/0x738\n"
- "> > > \302\240\302\240io_schedule+0x5c/0xc0\n"
- "> > > \302\240\302\240bit_wait_io+0xc/0x48\n"
- "> > > \302\240\302\240out_of_line_wait_on_bit+0x78/0xc0\n"
- "> > > \302\240\302\240do_get_write_access+0x1aa/0x4cc\n"
- "> > > \302\240\302\240jbd2_journal_get_write_access+0x32/0x74\n"
- "> > > \302\240\302\240__ext4_journal_get_write_access+0x3a/0xac\n"
- "> > > \302\240\302\240ext4_mb_mark_diskspace_used+0x66/0x5b0\n"
- "> > > \302\240\302\240ext4_mb_new_blocks+0x1ee/0x830\n"
- "> > > \302\240\302\240ext4_ext_map_blocks+0x504/0xcac\n"
- "> > > \302\240\302\240ext4_map_blocks+0x262/0x5e8\n"
- "> > > \302\240\302\240mpage_map_and_submit_extent+0xb8/0x648\n"
- "> > > \302\240\302\240ext4_writepages+0x5ce/0x6b4\n"
- "> > > \302\240\302\240do_writepages+0x20/0x84\n"
- "> > > \302\240\302\240__writeback_single_inode+0x2a/0x154\n"
- "> > > \302\240\302\240wb_writeback+0x538/0xae0\n"
- "> > > \302\240\302\240wb_workfn+0x17c/0x334\n"
- "> > > \302\240\302\240process_one_work+0x1a6/0x350\n"
- "> > > \302\240\302\240worker_thread+0xf2/0x478\n"
- "> > > \302\240\302\240kthread+0x120/0x13c\n"
- "> > > \302\240\302\240ret_from_fork+0x18/0x1c\n"
+ "> > > ??__switch_to+0x0/0xac\n"
+ "> > > ??__schedule+0x1b8/0x738\n"
+ "> > > ??io_schedule+0x5c/0xc0\n"
+ "> > > ??bit_wait_io+0xc/0x48\n"
+ "> > > ??out_of_line_wait_on_bit+0x78/0xc0\n"
+ "> > > ??do_get_write_access+0x1aa/0x4cc\n"
+ "> > > ??jbd2_journal_get_write_access+0x32/0x74\n"
+ "> > > ??__ext4_journal_get_write_access+0x3a/0xac\n"
+ "> > > ??ext4_mb_mark_diskspace_used+0x66/0x5b0\n"
+ "> > > ??ext4_mb_new_blocks+0x1ee/0x830\n"
+ "> > > ??ext4_ext_map_blocks+0x504/0xcac\n"
+ "> > > ??ext4_map_blocks+0x262/0x5e8\n"
+ "> > > ??mpage_map_and_submit_extent+0xb8/0x648\n"
+ "> > > ??ext4_writepages+0x5ce/0x6b4\n"
+ "> > > ??do_writepages+0x20/0x84\n"
+ "> > > ??__writeback_single_inode+0x2a/0x154\n"
+ "> > > ??wb_writeback+0x538/0xae0\n"
+ "> > > ??wb_workfn+0x17c/0x334\n"
+ "> > > ??process_one_work+0x1a6/0x350\n"
+ "> > > ??worker_thread+0xf2/0x478\n"
+ "> > > ??kthread+0x120/0x13c\n"
+ "> > > ??ret_from_fork+0x18/0x1c\n"
  "> > \n"
  "> > There are some details of hsdk_defconfig presented bellow:\n"
  "> > \n"
@@ -77,7 +66,7 @@
  "> > still it is strange, that some process is running in kernel space for a long time (at least 10sec).\n"
  "> > What is strange, before metioned commit I can't reproduce this behaviour.\n"
  "> > \n"
- "> > I am wondering is this expected behaviour?\302\240\n"
+ "> > I am wondering is this expected behaviour??\n"
  "> \n"
  "> Was the performance affected? i.e. the results from bonnie++\n"
  "I have run bonnie++ several times before and after mentioned commit. Here is output:\n"
@@ -91,7 +80,7 @@
  "ARCLinux,512M,5159,42,6944,1,5658,0,12945,99,344290,100,+++++,+++,16,22295,100,+++++,+++,32715,99,22888,99,+++++,+++,32007,99\n"
  "ARCLinux,512M,5170,42,6840,2,5315,0,12946,99,343889,100,+++++,+++,16,22445,100,+++++,+++,32681,99,22967,100,+++++,+++,32117,99\n"
  "--------------------------------------------------<8------------------------------------------------------------------------\n"
- "              ^^^^\302\240\n"
+ "              ^^^^?\n"
  "If i understand correctly, in third column is shown \"sequential output\" per character speed (K/sec), which decreased.\n"
  "\n"
  "> What mount options did you use?\n"
@@ -99,10 +88,6 @@
  "# mount /dev/mmcblk0p1 /mnt\n"
  "\n"
  "Best regards,\n"
- "Evgeniy Didin\n"
- "_______________________________________________\n"
- "linux-snps-arc mailing list\n"
- "linux-snps-arc@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-snps-arc
+ Evgeniy Didin
 
-a342081c06891bceaf54a006fc4264ebdf996a700f7f7f140e4a955216b184bc
+c91fd9930a0371b82bbb4dbf58643ef97180a9532a82eaca2d39e9f11f1d5002
