linux-ext4 - [Bug 200681] [inline_data] read() does not see what write() has just written through different FD in the same thread

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] [day] [month] [year] [list]

Message-ID: <bug-200681-13602-VxCfgeoWgo@https.bugzilla.kernel.org/>
Date:   Sun, 14 Oct 2018 07:29:22 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 200681] [inline_data] read() does not see what write() has just
 written through different FD in the same thread

https://bugzilla.kernel.org/show_bug.cgi?id=200681

--- Comment #9 from Anatoly Trosinenko (anatoly.trosinenko@...il.com) ---
> I'm curious how you found this bug; were you deliberately using a 1k block
> size, or were you trying to use inline_data with very small file systems?

Frankly speaking, I have not stumbled upon this bug in real life --- just done
some FS fuzzing and for improving performance used smaller FS images. Maybe
smaller images have larger probability of triggering some bugs in my setup, too
(now I know why :) ). But inline_data (as well as other extended options) were
enabled deliberately, of course, supposing they are less stable than the core
features.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.