From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752610Ab2AQIq4 (ORCPT ); Tue, 17 Jan 2012 03:46:56 -0500 Received: from one.firstfloor.org ([213.235.205.2]:56379 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752414Ab2AQIqz (ORCPT ); Tue, 17 Jan 2012 03:46:55 -0500 Date: Tue, 17 Jan 2012 09:46:50 +0100 From: Andi Kleen To: Li Zefan Cc: Chris Mason , Andi Kleen , linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org Subject: Re: Updated btrfs/crypto snappy interface ready for merging Message-ID: <20120117084650.GP11715@one.firstfloor.org> References: <1326414530-10789-1-git-send-email-andi@firstfloor.org> <20120116135442.GA28487@shiny> <4F1534FD.30707@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F1534FD.30707@cn.fujitsu.com> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > It's because decompressing inline extents always fails. I've fixed it > and will send the patch out in a new mail thread. Thanks for fixing. > > But seems there's bug in lib snappy code, which makes the decompressed > data doesn't quite match the original data. > > Simply copy a file to a btrfs filesystem with snappy enabled, and clear > page cache, and check the file: Hmm weird, I have never seen this. Do you have a reproducer? The basic compression code is quite well tested, I have a reasonable unit test. -Andi