| 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: <20140613103216.GA4589@amd.pavel.ucw.cz> Date: Fri, 13 Jun 2014 12:32:16 +0200 From: Pavel Machek <pavel@....cz> To: Dave Chinner <david@...morbit.com> Cc: Daniel Phillips <daniel@...nq.net>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, tux3@...3.org, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [RFC] Tux3 for review Hi! > > As I said, the glaring omission is proper ENOSPC handling, which is > > work in progress. I do not view that as an obstacle to merging. > > > > After all, Btrfs did not have proper ENOSPC handling when it was > > merged. > > Yup, and that was a big mistake. Hence not having working ENOSPC > detection is a major strike against merging a new filesystem now. Hmm, it seems that merging filesystems is getting harder over time. Soon, it will be impossible to merge new filesystem. > > The design is here: > > So come back when you've implemented it properly and proven that you > have a sound design and clean implementation. People submit code early to get feedback... but this is not exactly helpful feedback, I'm afraid... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists