GNU bug report logs -
#24118
25.1; [PATCH] Fix a possible crash caused by mapcar1
Previous Next
Reported by: Chris Feng <chris.w.feng <at> gmail.com>
Date: Sun, 31 Jul 2016 12:48:01 UTC
Severity: normal
Tags: patch
Found in version 25.1
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 2 Aug 2016 18:15:53 -0700
with message-id <8ad02288-7280-31c3-1a74-12a677107ca9 <at> cs.ucla.edu>
and subject line Re: 25.1; [PATCH] Fix a possible crash caused by mapcar1
has caused the debbugs.gnu.org bug report #24118,
regarding 25.1; [PATCH] Fix a possible crash caused by mapcar1
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
24118: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24118
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Processing a list with `mapcar' or `mapconcat' can be terminated early
when the list is tampered (as shown in the following example), and as a
result we'll be dealing with uninitialized memory which will likely
trigger a crash.
(setq a (make-list 10 0))
(mapcar (lambda (_)
(setcdr a nil))
a)
Chris
---
* src/fns.c (mapcar1): Check and reset uninitialized list elements.
---
src/fns.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/fns.c b/src/fns.c
index d5a1f74..1804bce 100644
--- a/src/fns.c
+++ b/src/fns.c
@@ -2524,6 +2524,10 @@ mapcar1 (EMACS_INT leni, Lisp_Object *vals, Lisp_Object fn, Lisp_Object seq)
vals[i] = dummy;
tail = XCDR (tail);
}
+
+ /* In case the list was tampered and the loop terminated early. */
+ if (i < leni)
+ memclear (vals + i, (leni - i) * word_size);
}
}
--
2.8.1
[Message part 3 (message/rfc822, inline)]
[Message part 4 (text/plain, inline)]
Thanks for the bug report. I installed the attached more-adventurous patch,
which truncates the result rather than extending it with nils. This seems a bit
more appropriate anyway.
Although it no longer matters for this patch, memclear is specified to store nil
values regardless of how nil is represented. Of course memclear's current
implementation assumes Qnil is zero, and memclear can't be portably and easily
implemented if we merely change Qnil to be nonzero, but that's a bridge we don't
have to cross unless we change Qnil to be nonzero.
[0001-Fix-mapcar-F-S-crash-when-F-alters-S-s-length.txt (text/plain, attachment)]
This bug report was last modified 8 years and 290 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.