From nobody@FreeBSD.org  Thu Jan  8 20:38:18 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 49C2616A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  8 Jan 2004 20:38:18 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7911543D31
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  8 Jan 2004 20:38:17 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i094cHdL042502
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 8 Jan 2004 20:38:17 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id i094cHUp042500;
	Thu, 8 Jan 2004 20:38:17 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200401090438.i094cHUp042500@www.freebsd.org>
Date: Thu, 8 Jan 2004 20:38:17 -0800 (PST)
From: Jean <bouloumag@hotmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Port linux_base-8-8.0_3: bash ls -l cause coredump
X-Send-Pr-Version: www-2.0

>Number:         61108
>Category:       kern
>Synopsis:       Port linux_base-8-8.0_3: bash ls -l cause coredump
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kensmith
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 08 20:40:09 PST 2004
>Closed-Date:    Sat Dec 17 01:05:06 GMT 2005
>Last-Modified:  Sat Dec 17 01:05:06 GMT 2005
>Originator:     Jean
>Release:        5.1-RELEASE
>Organization:
>Environment:
FreeBSD asterix.local.qc 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Mon Jul 28 18:06:43 EDT 2003     root@asterix.local.qc:/usr/obj/usr/src/sys/ASTERIX  i386    
>Description:
The builtin bash command ls, called with option -l cause a core dump in linux_base-8-8.0_3.
>How-To-Repeat:
    If I start a new shell with the command
# /usr/compat/linux/bin/bash

and enter the command 
# ls -l ~

in this new shell, I get a core dump (file ls.core)  
>Fix:
      
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-bugs->trevor 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Fri Jan 9 00:52:02 PST 2004 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61108 
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Thu Jun 24 23:52:41 GMT 2004 
State-Changed-Why:  
Has there been any progress on this one? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61108 

From: "Volker Stolz" <vs@freebsd.org>
To: freebsd-gnats-submit@freebsd.org, bouloumag@hotmail.com
Cc:  
Subject: Re: ports/61108: Port linux_base-8-8.0_3: bash ls -l cause coredump
Date: Tue, 20 Jul 2004 19:15:16 +0200

 I can't reproduce this in a 4.10 chrooted installation. Can you send us  
 the backtrace please?
 
 Volker

From: "Jean Darcoux" <bouloumag@hotmail.com>
To: vs@freebsd.org, freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: ports/61108: Port linux_base-8-8.0_3: bash ls -l cause coredump
Date: Tue, 20 Jul 2004 22:36:34 +0000

 >From: "Volker Stolz" <vs@freebsd.org>
 >To: freebsd-gnats-submit@freebsd.org, bouloumag@hotmail.com
 >Subject: Re: ports/61108: Port linux_base-8-8.0_3: bash ls -l cause 
 >coredump
 >Date: Tue, 20 Jul 2004 19:15:16 +0200
 >
 >I can't reproduce this in a 4.10 chrooted installation. Can you send us  
 >the backtrace please?
 
 I think that the problem was from an incorrect upgrade of the port. I had 
 other linux*_7.x port and maybe this is the cause of the coredump (bad 
 librairy ?). After removing that ports and reinstalling everything at 
 version 8-8.x I was not able to reproduce the bug. I think that the solution 
 for this bug is to remove the conflicting package (version 7.x) when 
 upgrading or installing 8.x.
 
 Best Regards,
 
 _________________________________________________________________
 Balayez vos courriels entrants et sortants et les pices jointes et 
 contribuez  liminer les virus destructeurs susceptibles dy tre intgrs. 
   http://join.msn.com/?pgmarket=fr-ca&page=features/virus Commencez ds 
 maintenant  profiter de tous les avantages de MSN Premium et obtenez les 
 deux premiers mois GRATUITS*.
 
State-Changed-From-To: feedback->closed 
State-Changed-By: vs 
State-Changed-When: Wed Jul 21 06:31:57 GMT 2004 
State-Changed-Why:  
Submitter believes this to be a conflict between linux_base 7 & 8 
and a botched update. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61108 
State-Changed-From-To: closed->open 
State-Changed-By: trevor 
State-Changed-When: Wed Jul 21 06:40:37 GMT 2004 
State-Changed-Why:  
I've seen this problem too, and I think I had a clean /compat/linux/ 
at the time. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61108 
Responsible-Changed-From-To: trevor->kensmith 
Responsible-Changed-By: trevor 
Responsible-Changed-When: Sun Jan 16 00:48:24 GMT 2005 
Responsible-Changed-Why:  

Ken Smith has been working on this problem.  He has MFCd the getxattr
syscall to RELENG_4.

http://www.freebsd.org/cgi/query-pr.cgi?pr=61108 
State-Changed-From-To: open->closed 
State-Changed-By: lawrance 
State-Changed-When: Sat Dec 17 01:01:33 UTC 2005 
State-Changed-Why:  
Submitter's port version and environment are very old now. 

vs@ could not reproduce the problem, and I can't reproduce 
it in a more recent environment. I think it is reasonable 
to assume that either the submitter's original diagnosis 
was correct (botched upgrade), or the problem is fixed now. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=61108 
>Unformatted:
