From 6f9c0342f33f52a2bda98d3709fbefd678bd46d9 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tschwinge@gnu.org>
Date: Sun, 13 May 2012 06:06:11 +0200
Subject: IRC.

---
 open_issues/glibc/getlogin_r.mdwn | 45 +++++++++++++++++++++++++++++++++++++++
 open_issues/glibc/octave.mdwn     | 35 ++++++++++++++++++++++++++++++
 2 files changed, 80 insertions(+)
 create mode 100644 open_issues/glibc/getlogin_r.mdwn
 create mode 100644 open_issues/glibc/octave.mdwn

(limited to 'open_issues/glibc')

diff --git a/open_issues/glibc/getlogin_r.mdwn b/open_issues/glibc/getlogin_r.mdwn
new file mode 100644
index 00000000..9980ea1f
--- /dev/null
+++ b/open_issues/glibc/getlogin_r.mdwn
@@ -0,0 +1,45 @@
+[[!meta copyright="Copyright © 2012 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
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!meta title="getlogin_r"]]
+
+[[!tag open_issue_glibc]]
+
+
+# IRC, freenode, #hurd, 2012-04-23
+
+    * pinotree spots how our getlogin_r() implementation uses a static
+        buffer...
+    <braunr> oO
+    <pinotree> braunr: yeah, the _r means "reentrantbutnotreally" xD
+    <braunr> pinotree: that's amazing ..
+    <antrik> pinotree: without having checked the actual implementation, that
+      doesn't sound like a problem...
+    <antrik> caching doesn't break reentrancy. the problem with the plain
+      getlogin() is that a static buffer is *returned to the user*
+    <pinotree> antrik: http://paste.debian.net/164727/
+    <braunr> ah, caching
+    <pinotree> i don't think this is caching at all
+    <antrik> pinotree: OK, not actually caching... but same effect as far as I
+      can tell
+    <antrik> pinotree: or is it the fixed size of the temporary variable you
+      are concerned about?
+    <pinotree> antrik: my concern was about the "static" of the buffer used for
+      the get_login rpc
+    <antrik> pinotree: I'm not sure that's a problem. can the login actually
+      ever change for a running process?
+    <pinotree> dunno
+    <pinotree> but if so, it would be pointless to do the rpc every time
+      instead of just once
+    <antrik> pinotree: true
+    * pinotree would just make it non-static and be safe
+    <antrik> pinotree: well, one might argue that allocating a KiB of stack
+      space is not very friendly, especially in a low-level library...
+    <antrik> not sure what the general policy is about such things in libc
diff --git a/open_issues/glibc/octave.mdwn b/open_issues/glibc/octave.mdwn
new file mode 100644
index 00000000..b12b7558
--- /dev/null
+++ b/open_issues/glibc/octave.mdwn
@@ -0,0 +1,35 @@
+[[!meta copyright="Copyright © 2012 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
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_glibc]]
+
+
+# IRC, OFTC, #debian-hurd, 2012-04-23
+
+    <pinotree> diffing the octave i386 vs hurd-i386 build logs gives
+      interesting surprises
+    <youpi>   checking whether this system has an arbitrary file name length
+      limit... no              |  checking whether this system has an arbitrary
+      file name length limit... yes
+    <youpi> ?
+    <pinotree> not only that
+    <youpi>   checking whether getcwd handles long file names properly... yes
+      |  checking whether getcwd handles long file names properly... no, but it
+      is partly worki+
+    <youpi> ?
+    <pinotree> -checking whether fdopendir works... yes
+    <pinotree> +checking whether fdopendir works... no
+    <pinotree> (- is i386, + is hurd-i386)
+    <pinotree> -checking whether getlogin_r works with small buffers... yes
+    <pinotree> +checking whether getlogin_r works with small buffers... no
+    <pinotree> -checking for working mkstemp... yes
+    <pinotree> +checking for working mkstemp... no
+    <pinotree> +checking for working nanosleep... no (mishandles large
+      arguments)
-- 
cgit v1.2.3