Date: Mon, 15 Apr 2024 22:01:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 193124] GELI data integrity verification should consider sparse zero pass-through Message-ID: <bug-193124-227-N12vFKvKSs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193124-227@https.bugs.freebsd.org/bugzilla/> References: <bug-193124-227@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=3D193124 Xin LI <delphij@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |delphij@FreeBSD.org Resolution|--- |Not Accepted Status|New |Closed --- Comment #1 from Xin LI <delphij@FreeBSD.org> --- Although I think this is an useful feature request to some extent, it's not really trivial to implement because in order to support it the GELI model h= as to keep track of which block is presumed to be zero's, and that bookkeeping information has to be stored somewhere. There are legitimate reasons to al= ways perform full initialization of the provider, by the way, because the size of data stored in the encrypted storage is revealed if that's not done, for example. A more generic solution would probably be making GELI init to perform the initialization in background and have it mark the provider as "need initialization", and upon attach the provider initializes itself in the background. This, however, would complicate the provider quite a bit becau= se it needs to be able to recover from power outage, etc. without damaging dat= a.=20 (This may be a good candidate for a summer of project project). --=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-193124-227-N12vFKvKSs>