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
| ||
|
Date: Thu, 17 May 2007 23:58:49 +0300 From: Pekka Enberg <penberg@...helsinki.fi> To: "Jörn Engel" <joern@...ybastard.org> CC: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org, akpm@...l.org, Albert Cahalan <acahalan@...il.com>, Thomas Gleixner <tglx@...utronix.de>, Jan Engelhardt <jengelh@...ux01.gwdg.de>, Evgeniy Polyakov <johnpol@....mipt.ru>, Greg KH <greg@...ah.com>, Ingo Oeser <ioe-lkml@...eria.de> Subject: Re: [PATCH] LogFS take three Jörn Engel wrote: > Compressing random data will actually enlarge it. If that happens I > simply store the verbatim uncompressed data instead and mark it as such. > > There is also demand for a user-controlled bit in the inode to disable > compression completely. All those .jpg, .mpg, .mp3, etc. just waste > time by trying and failing to compress them. So any sane way to enable compression is on per-inode basis which makes me still wonder why you need per-object compression. - 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