| lists.openwall.net | 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
| ||
|
Message-Id: <201001031211.o03CBvL3007984@demeter.kernel.org> Date: Sun, 3 Jan 2010 12:11:57 GMT From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 14972] [regression] msync() call on ext4 causes disk thrashing http://bugzilla.kernel.org/show_bug.cgi?id=14972 --- Comment #8 from Theodore Tso <tytso@....edu> 2010-01-03 12:11:56 --- I'm not sure why you are getting the device busy or resource busy error to the BLKTRACESETUP ioctl. Are you sure this is a kernel with the blktrace support configured in? And I assume the '#' error message indicates that you are running as root. You don't have SELinux or some other LSM configured, do you? Blktrace running alone does not produce output; it produces trace files for each CPU that can be parsed using the blkparse program. If you look back, you'll see that I suggested running the btrace program after you install the blktrace package. The btrace program is a convenience script which runs blktrace and blkparse to produce immediate output to standard out. There are man pages for blktrace, blkparse, and btrace which should have been installed when you installed the binaries for blktrace. Still, it shouldn't have spit out those error messages.... -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists