lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 3 Sep 2012 18:02:13 -0400
Subject: Weird filesystem corruption from wayland / radeon / chromium

[732715.730069] EXT4-fs error (device sda1): ext4_ext_search_left:1275: inode #21374007: comm flush-8:0: ix (10742) != EXT_FIRST_INDEX (0)
[  496.347230] EXT4-fs error (device sda1): ext4_ext_search_left:1275: inode #21374007: comm flush-8:0:ix (10742) != EXT_FIRST_INDEX (0)

Same search_left... argument?  Same inode?

$ sudo find . -inum 21374007 -print

My post about it to the wayland mailing list:

This happened running wayland with xwayland ( running as a rootless
wayland client) using RAOF's modified Radeon DDX (X driver).  I was
running chromium this time it happened, there is some possibility I had
not run chromium since the last time it happened and did run it then,
I'm not sure.

What is the significance of this file?  What does the error mean?

It seems like this shouldn't be possible.  What could be causing it?
Someone mentioned this could be the result of something "scribbling over
kernel memory".  Do these errors, and their similarity, provide any
insight into how to track it down?

The errors were three months apart.  They corresponded to filesystem
corruption.  Because of that I didn't run xwayland for the three months

"When we remember we are all mad, the mysteries of life disappear and
life stands explained." - Mark Twain
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists