After rebuilding redo logs, InnoDB can leak data from redo log buffer

encryption.innodb_encrypt_log_corruption 'innodb' w4 [ fail ]

        Test ended at 2017-06-23 09:43:46

CURRENT_TEST: encryption.innodb_encrypt_log_corruption

--- /usr/local/mariadb-10.2.7-linux-x86_64/mysql-test/suite/encryption/r/innodb_encrypt_log_corruption.result	2017-06-23 09:02:40.000000000 +0200

+++ /usr/local/mariadb-10.2.7-linux-x86_64/mysql-test/suite/encryption/r/innodb_encrypt_log_corruption.reject	2017-06-23 09:43:46.000000000 +0200

@@ -70,7 +70,7 @@

 FOUND 1 /InnoDB: MLOG_FILE_NAME incorrect:bogus/ in mysqld.1.err

 FOUND 1 /InnoDB: ############### CORRUPT LOG RECORD FOUND ##################/ in mysqld.1.err

 FOUND 1 /InnoDB: Log record type 55, page 151:488\. Log parsing proceeded successfully up to 1213973\. Previous log record type 56, is multi 0 Recv offset 9, prev 0/ in mysqld.1.err

-FOUND 1 /len 22. hex 38000000000012860cb7809781e80006626f67757300. asc 8               bogus / in mysqld.1.err

+NOT FOUND /len 22. hex 38000000000012860cb7809781e80006626f67757300. asc 8               bogus / in mysqld.1.err

 FOUND 1 /InnoDB: Set innodb_force_recovery to ignore this error/ in mysqld.1.err

 # Test a corrupted MLOG_FILE_NAME record.

 # valid header, invalid checkpoint 1, valid checkpoint 2, invalid block

mysqltest: Result length mismatch