commit | 8c5518ab1b5382bd047b5f16d8bd06e3c853705b | [log] [tgz] |
---|---|---|
author | Glenn Kasten <gkasten@google.com> | Mon Apr 17 16:34:38 2017 -0700 |
committer | Glenn Kasten <gkasten@google.com> | Mon Apr 17 16:53:06 2017 -0700 |
tree | f77769e5cb353000a5b7b22d7cf1dd9f60e2ab5b | |
parent | a834562a91b97f8b2ab3a5d6ed99d778c071f2cf [diff] |
Add option to flush the entire buffer on -EOVERFLOW This was the previous behavior prior to commit fc3d70736e4c24cbdc8c91076013c01e487fd4d5. The new behavior introduced by that commit is to preserve as much of the buffer as possible. But that introduced a regression in applications with so many overflows that they can't recover. So now the flush is optional. Test: at bug Bug: 36725187 Change-Id: Ia728a754405c89b5c46fea598f987ddb9e1e26d8