| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTindRb2v8O3+aR6GkCo=xkT6h5rbHDnkF1L5AdKH@mail.gmail.com> Date: Fri, 7 Jan 2011 15:23:37 +0100 From: Olaf van der Spek <olafvdspek@...il.com> To: Neil Brown <neilb@...e.de> Cc: Christian Stroetmann <stroetmann@...olinux.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-ext4 <linux-ext4@...r.kernel.org>, "Ted Ts'o" <tytso@....edu>, Nick Piggin <npiggin@...il.com> Subject: Re: Atomic non-durable file write API On Thu, Dec 30, 2010 at 1:50 AM, Neil Brown <neilb@...e.de> wrote: > On Wed, 29 Dec 2010 18:14:04 +0100 Olaf van der Spek <olafvdspek@...il.com> > wrote: > >> On Wed, Dec 29, 2010 at 5:30 PM, Christian Stroetmann >> <stroetmann@...olinux.com> wrote: >> >> Additional steps compared to what? The temp file, fsync, rename case? >> > >> > read the paragraphs as a whole >> >> Reading stuff again isn't going to change my question. >> > > OK, the fun I over. I guess it is time to actually answer your question, > rather than just teasing you with partial answers and hints about performance > impact .... > > Your question, as I understand it is: > > You see a hypothetical problem for which you cannot see a solution in > Linux, but for which you also cannot present a concrete use-case where > this problem needs to be addresses. > You want to know what the recommended solution is. > > > The reality is that the solution was devises and implemented many years ago > and is deeply embedded in the core design principles of Unix and Linux. > The reason that you cannot present a use-case is that there isn't one. > Unix was design so that this hypothetical need will never arise. It's so hypothetical that a number of other comments on Ted's blog about this ask the same question: http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/#comment-1979 http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/#comment-1981 http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/#comment-1990 http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/#comment-1992 http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/#comment-2095 http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/#comment-2099 And many more. http://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/ Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists