Date: Wed, 6 Mar 2013 00:23:23 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: lev@FreeBSD.org Cc: mckusick@mckusick.com, freebsd-fs@FreeBSD.org Subject: Re: Panic in ffs_valloc (Was: Unexpected SU+J inconsistency AGAIN -- please, don't shift topic to ZFS!) Message-ID: <201303060823.r268NNor015235@gw.catspoiler.org> In-Reply-To: <958644234.20130306105205@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Mar, Lev Serebryakov wrote: > Hello, Don. > You wrote 6 марта 2013 г., 10:43:11: > > DL> When growing a file, the data *must* be written before writing the block > DL> pointer that points to it. If this ordering isn't obeyed, then a system > DL> crash that occurs between the block pointer write and the data write > DL> would result in the file containing whatever garbage was in the data > DL> block. That garbage could be the confidential contents of some other > DL> user's previously deleted file. > It is why confidential data should be zeored-out before file deletion > :) Performance when deleting multi-gigabyte, low-value files would kind of suck if we did that ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303060823.r268NNor015235>