http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57436
Bug ID: 57436
Summary: Linux kernel gives file system corruption when built
with gcc 4.8.0
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: a.radke at arcor dot de
Our ArchLinux distribution gives sort of reproducable file system corruption
with all kernels built with gcc 4.8.0 (currently at snapshot 20130502). The
same kernel built with gcc 4.7.3 is stable. glibc is 2.17, binutils 2.23.2.
Architecture is x86_64. I'm testing only stable long term kernel 3.0.xx branch
but kernel 3.8 showed the same error.
Our default flags:
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
The kernel builds well with gcc 4.8.0, the bug I'm running into is this: My
server running such a bad compiled kernel hosts a NFSv4 share on a XFS
formatted partition. On the same drive my dovecot imap server stores all mails.
When marking lots of small files on any fast client as read/unread the server
currupts the xfs file system with such messages:
imap(andyrtr):
Error:maildir_file_do(/mnt/share/andyrtr/Mail/.Mailinglisten.Linux-stable/cur/msg.MFVZBC:2,):
Filename keeps changing
Usually these are ACL related messages. After a reboot the related mail files
are sometimes gone and sometimes can be fixed with xfs_repair.
Any idea what this could be and how to track this down? It's a pretty nasty bug
in gcc it seems to me. I can provide further info if needed.