commit 03539407b0208fadba3d3f3a9b8c3cd899228b67
author Glenn Kasten <gkasten@google.com> Mon Apr 17 16:40:46 2017 -0700
committer Glenn Kasten <gkasten@google.com> Mon Apr 17 16:53:33 2017 -0700
tree 17957b5bd513605f0c8392b12f1fec2977dc4c1c
parent 6cb102d4a1cbaaacecde61d4e2a261c910c55e1c

Use option to flush the entire buffer on -EOVERFLOW

This was the previous behavior prior to project system/media 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.
In the case of PipeReader, we do need the flush.

Test: at bug
Bug: 36725187
Change-Id: I25609c7a656a05228fb4e7d4082b2857f4195a34