Bug 143158

Summary:	cp causes segmentation fault
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Alexander Heger <novel>
Component:	Basesystem	Assignee:	Harald Mueller-Ney <hmuelle>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	requested information va_list processing fix

Description Alexander Heger 2006-01-13 17:20:49 UTC

runnung suse 10.0 with current updates on dual AMD 275 (dual core) w/ 8GB RAM.
When I try to copy files (similar for mv to a different device) I get a segmentation fault.  Independent of device.  Memory seems fine - I can allocate 7GB arrays with IDL.  FC4 does not show this problem on the same machine.

Comment 1 Michael Gross 2006-01-16 14:45:24 UTC

Please be a little more verbose. Provide more detailed information about your hardware (`hwinfo') and how large the copied files are. Also, attach 500 lines of your syslog. To debug this, we'll also need a backtrace which could be created with gdb or strace/ltrace - the last 50 lines should be sufficient. Thanks.

Comment 2 Alexander Heger 2006-01-16 22:24:32 UTC

Created attachment 63516 [details]
requested information

I supplied the requested information plus a bried demonstration.  The segmentation fault seems to occur after the cp operation is complete - but mv among different devices does not work with this bug being present (it does work on the same device).  It does not seem to depend on file size (same for small files of a few kb).  Attached file is gzipped archive file.

Comment 3 Michael Gross 2006-01-17 14:14:31 UTC

Andreas: Please look into it. This could also be a kernel problem, in that case, just assign it back to us or reassign.

Comment 4 Andreas Schwab 2006-01-17 16:11:44 UTC

ACL problem.

Comment 5 Andreas Gruenbacher 2006-01-20 17:40:34 UTC

Alexander, I could not reproduce, yet. Could you please regenerate the ltrace with the -S option so that we'll see how setxattr fails? Thanks!

Comment 6 Andreas Gruenbacher 2006-01-20 18:34:22 UTC

Created attachment 64333 [details]
va_list processing fix

Does this fix help?

Comment 7 Andreas Gruenbacher 2006-01-26 14:09:42 UTC

Ping

Comment 8 Andreas Gruenbacher 2006-01-30 16:05:16 UTC

I'm assuming that this bug is fixed with the patch in comment 6.

Andreas, this bug does not trigger very often, but it should still get fixed, at least in 10.0. I have submitted packages and a patchinfo file for 9.2, 9.3, and 10.0. Other distributions are not affected. Please decide for which distributions to push out the fix. Thanks.

Comment 9 Andreas Jaeger 2006-01-30 20:24:46 UTC

Fix it for 9.2, 9.3 and 10.0 - swamp ID is: Maintenance-Tracker-3449

Comment 11 Anja Stock 2006-02-01 10:19:43 UTC

released
Patchinfo was ok :-)