diff options
| author | rvargas@google.com <rvargas@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-04 17:34:38 +0000 |
|---|---|---|
| committer | rvargas@google.com <rvargas@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-04 17:34:38 +0000 |
| commit | 42d5be693f7cc623caa3df6bfb2bcc4f6861cb36 (patch) | |
| tree | e5defa1e3d5ba1f662aaebd6eaa70e0f08a76027 /base/file_util_win.cc | |
| parent | 05f06dfc585db57c544bca907e74d5e6d4ca6982 (diff) | |
| download | chromium_src-42d5be693f7cc623caa3df6bfb2bcc4f6861cb36.zip chromium_src-42d5be693f7cc623caa3df6bfb2bcc4f6861cb36.tar.gz chromium_src-42d5be693f7cc623caa3df6bfb2bcc4f6861cb36.tar.bz2 | |
Disk cache: Don't return zeros when reading from an entry
that has a buffer with an offset beyond the start of the
read.
The read logic was incorrectly calculating the eof for an
entry as the current size minus the unreported size, so it
was assuming that a buffer with a large offset was always
extending the file... so it was returning zeros for the data.
Now we don't attempt to keep buffers that extend a file, and
the eof computation was fixed to be just the current lenght.
BUG=59275
TEST=net_unittests
Review URL: http://codereview.chromium.org/4289004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65074 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/file_util_win.cc')
0 files changed, 0 insertions, 0 deletions