Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
d2a4073d
Commit
d2a4073d
authored
Sep 26, 2015
by
Raymond Hettinger
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Issue #25135: Avoid possible reentrancy issues in deque_clear.
parent
8bfacc79
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
60 additions
and
3 deletions
+60
-3
Misc/NEWS
Misc/NEWS
+3
-0
Modules/_collectionsmodule.c
Modules/_collectionsmodule.c
+57
-3
No files found.
Misc/NEWS
View file @
d2a4073d
...
...
@@ -40,6 +40,9 @@ Library
-
Issue
#
19143
:
platform
module
now
reads
Windows
version
from
kernel32
.
dll
to
avoid
compatibility
shims
.
-
Issue
#
25135
:
Make
deque_clear
()
safer
by
emptying
the
deque
before
clearing
.
This
helps
avoid
possible
reentrancy
issues
.
-
Issue
#
24684
:
socket
.
socket
.
getaddrinfo
()
now
calls
PyUnicode_AsEncodedString
()
instead
of
calling
the
encode
()
method
of
the
host
,
to
handle
correctly
custom
unicode
string
with
an
encode
()
method
...
...
Modules/_collectionsmodule.c
View file @
d2a4073d
...
...
@@ -644,16 +644,70 @@ PyDoc_STRVAR(remove_doc,
static
void
deque_clear
(
dequeobject
*
deque
)
{
block
*
b
;
block
*
prevblock
;
block
*
leftblock
;
Py_ssize_t
leftindex
;
Py_ssize_t
n
;
PyObject
*
item
;
/* During the process of clearing a deque, decrefs can cause the
deque to mutate. To avoid fatal confusion, we have to make the
deque empty before clearing the blocks and never refer to
anything via deque->ref while clearing. (This is the same
technique used for clearing lists, sets, and dicts.)
Making the deque empty requires allocating a new empty block. In
the unlikely event that memory is full, we fall back to an
alternate method that doesn't require a new block. Repeating
pops in a while-loop is slower, possibly re-entrant (and a clever
adversary could cause it to never terminate).
*/
b
=
newblock
(
NULL
,
NULL
,
0
);
if
(
b
==
NULL
)
{
PyErr_Clear
();
goto
alternate_method
;
}
/* Remember the old size, leftblock, and leftindex */
leftblock
=
deque
->
leftblock
;
leftindex
=
deque
->
leftindex
;
n
=
deque
->
len
;
/* Set the deque to be empty using the newly allocated block */
deque
->
len
=
0
;
deque
->
leftblock
=
b
;
deque
->
rightblock
=
b
;
deque
->
leftindex
=
CENTER
+
1
;
deque
->
rightindex
=
CENTER
;
deque
->
state
++
;
/* Now the old size, leftblock, and leftindex are disconnected from
the empty deque and we can use them to decref the pointers.
*/
while
(
n
--
)
{
item
=
leftblock
->
data
[
leftindex
];
Py_DECREF
(
item
);
leftindex
++
;
if
(
leftindex
==
BLOCKLEN
&&
n
)
{
assert
(
leftblock
->
rightlink
!=
NULL
);
prevblock
=
leftblock
;
leftblock
=
leftblock
->
rightlink
;
leftindex
=
0
;
freeblock
(
prevblock
);
}
}
assert
(
leftblock
->
rightlink
==
NULL
);
freeblock
(
leftblock
);
return
;
alternate_method:
while
(
deque
->
len
)
{
item
=
deque_pop
(
deque
,
NULL
);
assert
(
item
!=
NULL
);
Py_DECREF
(
item
);
}
assert
(
deque
->
leftblock
==
deque
->
rightblock
&&
deque
->
leftindex
-
1
==
deque
->
rightindex
&&
deque
->
len
==
0
);
}
static
PyObject
*
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment