[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Weird bug: system instability after cat /proc/kcore


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Michael Marineau" <mike@xxxxxxxxxxxx>
  • Date: Wed, 3 Oct 2007 16:03:15 -0700
  • Delivery-date: Wed, 03 Oct 2007 16:04:02 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=YmInJZNq63tsRQFD352ch4262DKZI6zAvhu6HYXOLsfFauVTZypawZGHI4tOX+WZVgLjg2khfuUZKYr3unqb4/ZPOzx3pDLdkDklG/GWngpA7lmG0uqBrl31X+zFdlU3jwt3Jpa5556K1z+itsPblYziK7KpuvHhx5X6U9r49TM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Ok, the existence of this bug just blew my mind. It appears that after
coppying /proc/kcore to disk the system starts to behave strangely.
Processes start to sometimes segfault randomly or die with a glibc
double free error. The system is perfectly fine prior to catting
/proc/kcore. I can reproduce this problem on the 2.6.18 kernel from
xen 3.1.0 and 3.1.1-rc2. To trigger it I just have to run 'cat
/proc/kcore >coredump' and then start hitting the system with
something like a gdb compile.  I usually see a segfault or some
strange failure before the compile finishes.

-- 
Michael Marineau
Oregon State University
mike@xxxxxxxxxxxx

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.