summaryrefslogtreecommitdiff
path: root/open_issues/ext2fs_libports_reference_counting_assertion.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/ext2fs_libports_reference_counting_assertion.mdwn')
-rw-r--r--open_issues/ext2fs_libports_reference_counting_assertion.mdwn13
1 files changed, 12 insertions, 1 deletions
diff --git a/open_issues/ext2fs_libports_reference_counting_assertion.mdwn b/open_issues/ext2fs_libports_reference_counting_assertion.mdwn
index ff1c4c38..9ff43afa 100644
--- a/open_issues/ext2fs_libports_reference_counting_assertion.mdwn
+++ b/open_issues/ext2fs_libports_reference_counting_assertion.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -91,3 +91,14 @@ With that patch in place, the assertion failure is seen more often.
sure we can get that easily lol
[[automatic_backtraces_when_assertions_hit]].
+
+
+# IRC, freenode, #hurd, 2013-10-09
+
+ <braunr> mhmm, i may have an explanation for the weird assertions we
+ sometimes see in ext2fs
+ <braunr> glibc uses alloca to reserve memory for one reply port per thread
+ in abort_all_rpcs
+ <braunr> if this erases the thread-specific area, we can expect all kinds
+ of wreckage
+ <braunr> i'm not sure how to fix this though