[Bug libc/16502] New: libc __nss_passwd_lookup

[Bug libc/16502] New: libc __nss_passwd_lookup

[marczakk at poczta dot onet.pl]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

            Bug ID: 16502
           Summary: libc __nss_passwd_lookup
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: marczakk at poczta dot onet.pl
                CC: drepper.fsp at gmail dot com

After install glibc-2.18-r1 on gentoo i have problem with running some apps
used jvm. 

Details:

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xf6bd5c7d, pid=6266, tid=4138243840
#
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) Client VM (20.45-b01 mixed mode, sharing linux-x86
)
# Problematic frame:
# C  [libc.so.6+0x12ac7d]  __nss_passwd_lookup+0x45d

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[marczakk at poczta dot onet.pl]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Chris <marczakk at poczta dot onet.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Chris <marczakk at poczta dot onet.pl> ---
Problem solved.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[siddhesh at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at redhat dot com
         Resolution|FIXED                       |INVALID

--- Comment #2 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
The problem was not solved in glibc sources, so it is obviously not a glibc bug
and hence, the bug should be closed as INVALID, not FIXED.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[marczakk at poczta dot onet.pl]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Chris <marczakk at poczta dot onet.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |FIXED

--- Comment #3 from Chris <marczakk at poczta dot onet.pl> ---
(In reply to Siddhesh Poyarekar from comment #2)
> The problem was not solved in glibc sources, so it is obviously not a glibc
> bug and hence, the bug should be closed as INVALID, not FIXED.

Patch concerned glibc sources, precisely sysdeps/x86_64/multiarch/strstr.c
b/sysdeps/x86_64/multiarch/strstr.c  file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[siddhesh at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

--- Comment #4 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
(In reply to Chris from comment #3)
> Patch concerned glibc sources, precisely sysdeps/x86_64/multiarch/strstr.c
> b/sysdeps/x86_64/multiarch/strstr.c  file.

Is this an upstream patch?  If so, please provide the git commit id so that
anyone referring to this bug would know what fixed it.  For all you know, it
could even be a duplicate of another existing bug.

If it is an upstream bug and you've fixed it for yourself and decided to not
contribute the patch upstream, then I would prefer to keep this bug open till
someone else runs into this bug and decides to post a patch to fix it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[marczakk at poczta dot onet.pl]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Chris <marczakk at poczta dot onet.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #5 from Chris <marczakk at poczta dot onet.pl> ---
(In reply to Siddhesh Poyarekar from comment #4)
> (In reply to Chris from comment #3)
> > Patch concerned glibc sources, precisely sysdeps/x86_64/multiarch/strstr.c
> > b/sysdeps/x86_64/multiarch/strstr.c  file.
> 
> Is this an upstream patch?  If so, please provide the git commit id so that
> anyone referring to this bug would know what fixed it.  For all you know, it
> could even be a duplicate of another existing bug.
> 
> If it is an upstream bug and you've fixed it for yourself and decided to not
> contribute the patch upstream, then I would prefer to keep this bug open
> till someone else runs into this bug and decides to post a patch to fix it.

I really don't care about yours "Status" of bug. I see it's most important
thing for you.

Patch is realy simple:

Source: .../sysdeps/x86_64/multiarch/strstr.c
b/sysdeps/x86_64/multiarch/strstr.c

--- a/sysdeps/x86_64/multiarch/strstr.c
+++ b/sysdeps/x86_64/multiarch/strstr.c
@@ -86,7 +86,7 @@
 /* Simple replacement of movdqu to address 4KB boundary cross issue.
    If EOS occurs within less than 16B before 4KB boundary, we don't
    cross to next page.  */
-static __m128i
+static inline __m128i
 __m128i_strloadu (const unsigned char * p, __m128i zero)
 {
   if (__builtin_expect ((int) ((size_t) p & 0xfff) > 0xff0, 0)) 


I dont't know sources of glibc but for me someone forgot to add "inline" to
__m128i_strloadu. After add it, everything works just fine. 

Lack of this caused errors in acroread too (access memory violation and it
douesn't work).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[allan at archlinux dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Allan McRae <allan at archlinux dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allan at archlinux dot org

--- Comment #6 from Allan McRae <allan at archlinux dot org> ---
This is the i686 issue with __strstr_sse42 and unaligned stack.  This has been
"fixed" by 1818483b.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[siddhesh at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #7 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
(In reply to Allan McRae from comment #6)
> This is the i686 issue with __strstr_sse42 and unaligned stack.  This has
> been "fixed" by 1818483b.

Thanks Allan - that's the patch the completes Ondrej's performance regression
fix in bug 12100.  The patch in comment 5 is no longer valid and may even be
simply hiding another bug.  I'll keep this open as UNCONFIRMED since we have no
information on why the crash occurs or why the patch fixes it.  If this bug is
still present in 2.19 (and a valid glibc bug), someone will hit it and
hopefully give some more information.

(In reply to Chris from comment #5)
> I really don't care about yours "Status" of bug. I see it's most important
> thing for you.

Good job mischaracterizing my concern.  If you cannot help with the development
and maintenance process then at least don't try to dictate how the process
should run.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[allan at archlinux dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

--- Comment #8 from Allan McRae <allan at archlinux dot org> ---
I should have been more clear.  This is a gcc bug that was exposed when
removing the inline statements.  Details are given in [1]. So removing the
SSE4.2 implementation completely removes this bug.

[1] https://sourceware.org/glibc/wiki/Release/2.18#Packaging_Changes

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[siddhesh at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #9 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
(In reply to Allan McRae from comment #8)
> I should have been more clear.  This is a gcc bug that was exposed when
> removing the inline statements.  Details are given in [1]. So removing the
> SSE4.2 implementation completely removes this bug.
> 
> [1] https://sourceware.org/glibc/wiki/Release/2.18#Packaging_Changes

Mid-air collision - that struck me the moment I hit submit.  Closing this as
duplicate of 12100.

*** This bug has been marked as a duplicate of bug 12100 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/16502] libc __nss_passwd_lookup

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16502

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.