Date: Sun, 23 Jul 2023 14:18:25 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 272678] VFS: Incorrect data in read from concurrent write Message-ID: <bug-272678-3630-EaK1oRo747@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272678-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-272678-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272678 --- Comment #2 from Andrew "RhodiumToad" Gierth <andrew@tao11.riddles.org.u= k> --- (In reply to Andrew "RhodiumToad" Gierth from comment #1) Concurrent truncate doesn't, so far in my testing, result in any crashes, b= ut it can cause the reader to read data with 0x00 in place of the original byt= es. i.e. file initially contains some non-zero bytes; read and ftruncate(fd,0) race; read might return non-zero bytes read based on the old length, but wi= th the data zeroed. (I noticed another comment in uiomove_object that said that the tmpfs vnode lock was held, even though it might not be.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272678-3630-EaK1oRo747>