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: <bug-105121-13602-vzkWbYmk7l@https.bugzilla.kernel.org/> Date: Mon, 28 Sep 2015 15:23:46 +0000 From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 105121] lseek(SEEK_DATA) hangs for a long time for sparse files in the page cache https://bugzilla.kernel.org/show_bug.cgi?id=105121 --- Comment #4 from ValdikSS <iam@...dikss.org.ru> --- Nobody really uses grep on sparse files. It was just a discussion on why many people use cat|grep instead of just using 'grep file', as pipes are usually slower. Somebody said that he uses cat|grep because it's actually faster than 'grep file' and made this test case. fallocate was used just to make big enough file to tell a difference in seconds. His result was 1 second with cat|grep and 3 seconds with grep file, but he was running btrfs. When I tried his test case, it hang grep so hard I couldn't kill it with SIGKILL even if it was in 'running' state. I took a look in strace what's going on and why it is stalled and filled this bug. Anyway, thanks for confirmation and acknowledgment this problem! -- 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