From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 200681] [inline_data] read() does not see what write() has just written through different FD in the same thread
Date: Sun, 14 Oct 2018 07:29:22 +0000 [thread overview]
Message-ID: <bug-200681-13602-VxCfgeoWgo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200681-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200681
--- Comment #9 from Anatoly Trosinenko (anatoly.trosinenko@gmail.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.
prev parent reply other threads:[~2018-10-14 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200681-13602@https.bugzilla.kernel.org/>
2018-10-13 16:03 ` [Bug 200681] [inline_data] read() does not see what write() has just written through different FD in the same thread bugzilla-daemon
2018-10-13 16:04 ` bugzilla-daemon
2018-10-13 21:25 ` bugzilla-daemon
2018-10-14 7:29 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-200681-13602-VxCfgeoWgo@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.