Issue #9295: Fix a crash under Windows when calling close() on a file

object with custom buffering from two threads at once.
This commit is contained in:
Antoine Pitrou 2010-10-28 14:50:57 +00:00
parent 658370e72c
commit 638cee62d5
2 changed files with 9 additions and 0 deletions

View File

@ -63,6 +63,9 @@ Core and Builtins
Library
-------
- Issue #9295: Fix a crash under Windows when calling close() on a file
object with custom buffering from two threads at once.
- Issue #5027: The standard ``xml`` namespace is now understood by
xml.sax.saxutils.XMLGenerator as being bound to
http://www.w3.org/XML/1998/namespace. Patch by Troy J. Farrell.

View File

@ -423,6 +423,7 @@ close_the_file(PyFileObject *f)
int sts = 0;
int (*local_close)(FILE *);
FILE *local_fp = f->f_fp;
char *local_setbuf = f->f_setbuf;
if (local_fp != NULL) {
local_close = f->f_close;
if (local_close != NULL && f->unlocked_count > 0) {
@ -446,10 +447,15 @@ close_the_file(PyFileObject *f)
* called. */
f->f_fp = NULL;
if (local_close != NULL) {
/* Issue #9295: must temporarily reset f_setbuf so that another
thread doesn't free it when running file_close() concurrently.
Otherwise this close() will crash when flushing the buffer. */
f->f_setbuf = NULL;
Py_BEGIN_ALLOW_THREADS
errno = 0;
sts = (*local_close)(local_fp);
Py_END_ALLOW_THREADS
f->f_setbuf = local_setbuf;
if (sts == EOF)
return PyErr_SetFromErrno(PyExc_IOError);
if (sts != 0)