linux-ext4 - [Bug 105121] lseek(SEEK_DATA) hangs for a long time for sparse files in the page cache

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Sep 2015 15:15:29 +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 #3 from Theodore Tso <tytso@....edu> ---
This implies that grep is using lseek(SEEK_DATA) as an optimization when users
use grep on sparse files.   So I'm guessing this is a Thing, but I'm at a loss
why people are interested in running grep on a sparse file (with or without
blocks preallocated using fallocate).   Can you enlighten me as to why people
(or at least you and your colleague) find it useful to run grep on such files?

Not that it matters since this is a pretty clear optimization we should add to
ext4; I'm just curious what the use case is.

Thanks!!

-- 
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