| Summary: | sys-apps/attr segfault on file copy during dev-dotnet/xsp merge | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Radoslaw Szkodzinski <astralstorm> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Full backtrace of the issue | ||
|
Description
Radoslaw Szkodzinski
2010-10-04 22:05:22 UTC
Created attachment 249597 [details]
Full backtrace of the issue
Sorry, forgot to mention: sys-apps/attr-2.4.44 and sys-apps/attr-2.4.43 fail in the same way. The stacktrace is from 2.4.44 Coreutils is version 8.5-r1. Merging coreutils with USE=-xattr works around the bug. Before you ask, I've checked w/o -fprefetch-loop-arrays and that's not responsible. try with a non-hardened kernel. at least Bug 300166 indicates this was the problem. 2.6.35.7-ck1+ - does that look hardened to you? :) Unless hardened gcc enabled something there for me... I did get warnings about missing SSP from this kernel. Possibly the same problem with SMACK, I have it enabled (and use it for some data). Might be the same thing as in that bug, SMACK creating some xattrs that make libattr explode. Is there an upstream bug report? Where is coreutils upstream now? *** This bug has been marked as a duplicate of bug 300166 *** |