[ 
https://issues.apache.org/jira/browse/HADOOP-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004720#comment-13004720
 ] 

Allen Wittenauer commented on HADOOP-7156:
------------------------------------------

> No, like any other documentation improvement it should wait for the 
> next release. Our definitive documentation lives in the source tree. 
> The fact that some of it is in the wiki doesn't change that.

I agree to a certain extent.  But listing a moving target from suffering from a 
problem that exists today that may not exist tomorrow for a release of our 
software that is still months out is a mistake.  CentOS 6.0 doesn't even exist 
yet in any official form yet we're declaring it bugged. 

> Assumedly if you've updated your pam manually to workaround this issue, 
> you'd know that, and you wouldn't turn on the config option!

What I am applying the 6-updates repo after a kick? Are packages from 
https://rhn.redhat.com/errata/rhel-server-6-errata.html not considered part of 
RHEL 6?  I suspect Red Hat would disagree.

I realize that for the majority of committers don't actually use an Apache 
release so this doesn't seem like a big deal since you folks release seemingly 
monthly, if not more frequent.  I also realize that in order for the various 
commercial interests involved it behooves them to get any and all patches 
committed to show that they are "contributing".  The reality is that by the 
time this patch shows up in an actual Apache release, it is bound to be 
outdated.... and that's where I take offense.


> getpwuid_r is not thread-safe on RHEL6
> --------------------------------------
>
>                 Key: HADOOP-7156
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7156
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>         Environment: RHEL 6.0 "Santiago"
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.22.0
>
>         Attachments: hadoop-7156.txt, hadoop-7156.txt, hadoop-7156.txt
>
>
> Due to the following bug in SSSD, functions like getpwuid_r are not 
> thread-safe in RHEL 6.0 if sssd is specified in /etc/nsswitch.conf (as it is 
> by default):
> https://fedorahosted.org/sssd/ticket/640
> This causes many fetch failures in the case that the native libraries are 
> available, since the SecureIO functions call getpwuid_r as part of fstat. By 
> enabling -Xcheck:jni I get the following trace on JVM crash:
> *** glibc detected *** /mnt/toolchain/JDK6u20-64bit/bin/java: free(): invalid 
> pointer: 0x0000003575741d23 ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x3575675676]
> /lib64/libnss_sss.so.2(_nss_sss_getpwuid_r+0x11b)[0x7fe716cb42cb]
> /lib64/libc.so.6(getpwuid_r+0xdd)[0x35756a5dfd]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to