Closed b510eab9-9bb7-4789-a06f-c0a1898e20d3 closed 13 years ago
mmapmodule.c's mmap_object_dealloc calls msync without checking for an error.
Do you have a test case to reproduce the errors?
I see that we call msync followed by munmap, neither one checked.
No, I don't know how to provoke such an error other than passing illegal parameters..(or munmap'ing the mmap'ed area).
I think this can be closed.
msync() is only called in mmap.flush() and it is checked for an error.
That was changed in r84950 from bpo-2643.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields: ```python assignee = None closed_at =
created_at =
labels = ['type-bug']
title = 'errors from msync ignored in mmap_object_dealloc'
updated_at =
user = 'https://bugs.python.org/schmir'
```
bugs.python.org fields:
```python
activity =
actor = 'brian.curtin'
assignee = 'none'
closed = True
closed_date =
closer = 'brian.curtin'
components = []
creation =
creator = 'schmir'
dependencies = []
files = []
hgrepos = []
issue_num = 2644
keywords = []
message_count = 5.0
messages = ['65553', '97573', '97583', '126414', '126433']
nosy_count = 3.0
nosy_names = ['schmir', 'brian.curtin', 'rosslagerwall']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2644'
versions = ['Python 2.6']
```