From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218648] New: ext4: previously opened file remains writeable on readonly ext4 filesystem; Data loss.
Date: Wed, 27 Mar 2024 09:31:57 +0000 [thread overview]
Message-ID: <bug-218648-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218648
Bug ID: 218648
Summary: ext4: previously opened file remains writeable on
readonly ext4 filesystem; Data loss.
Product: File System
Version: 2.5
Kernel Version: 6.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: zsolt@integrity.hu
Regression: No
I have a VM on KVM. The KVM image is on GlusterFS and for the test I stopped
the gluster server. If this backend goes offline, the ext4 filesystem will be
readonly in the VM. It's OK.
But if I have a previously opened file (for writing) in this ext4 filesystem. I
can continue to write. The "ls -l" command shows, the file is growing (but the
modification time isn't changes anymore).
Second test: previously mmap-ed file. I can rewrite the 4k blocks on readonly
ext4. Of course, this changes will be lost on reboot.
So the readonly filesystem blocked the new open for writing, but the prevously
opened file can I write, but the data will be lost.
Are these cases normal on readonly filesystem or a bug?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-03-27 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 9:31 bugzilla-daemon [this message]
2024-03-28 14:55 ` [Bug 218648] ext4: previously opened file remains writeable on readonly ext4 filesystem; Data loss bugzilla-daemon
2024-03-29 9:06 ` bugzilla-daemon
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-218648-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.