diff options
| author | junglefowl <junglefowl@riseup.net> | 2017-01-23 19:08:54 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2017-01-25 13:21:44 -0500 |
| commit | 373d9aff7af41c07bb51093df4ceb51a13404a44 (patch) | |
| tree | a1b6786bf56410c69202c6e1de8cadad11070faa /changes | |
| parent | 1130fd87edb38570dbad9c1a04adfe0947490b2d (diff) | |
| download | tor-373d9aff7af41c07bb51093df4ceb51a13404a44.tar.gz tor-373d9aff7af41c07bb51093df4ceb51a13404a44.zip | |
Fail if file is too large to mmap.
If tor_mmap_file is called with a file which is larger than SIZE_MAX,
only a small part of the file will be memory-mapped due to integer
truncation.
This can only realistically happen on 32 bit architectures with large
file support.
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/bug21134 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/bug21134 b/changes/bug21134 new file mode 100644 index 0000000000..b851718372 --- /dev/null +++ b/changes/bug21134 @@ -0,0 +1,5 @@ + o Minor bugfixes (portability): + - Do not silently truncate content of files if they are larger + than SIZE_MAX bytes. This issue could occur on 32 bit systems + with large file support and files which are larger than 4 GB. + Fixes bug 21134; bugfix on 0.3.0.1-alpha. |