From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754849AbdKNOw3 (ORCPT ); Tue, 14 Nov 2017 09:52:29 -0500 Received: from mx2.suse.de ([195.135.220.15]:45308 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752752AbdKNOwV (ORCPT ); Tue, 14 Nov 2017 09:52:21 -0500 Date: Tue, 14 Nov 2017 15:50:26 +0100 From: David Sterba To: Qu Wenruo Cc: David Sterba , torvalds@linux-foundation.org, clm@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] Btrfs changes for 4.15 Message-ID: <20171114145026.GE28899@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Qu Wenruo , David Sterba , torvalds@linux-foundation.org, clm@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 14, 2017 at 07:39:11AM +0800, Qu Wenruo wrote: > > - extend mount options to specify zlib compression level, -o compress=zlib:9 > > However the support for it has a big problem, it will cause wild memory > access for "-o compress" mount option. > > Kernel ASAN can detect it easily and we already have user report about > it. Btrfs/026 could also easily trigger it. > > The fixing patch is submitted some days ago: > https://patchwork.kernel.org/patch/10042553/ > > And the default compression level when not specified is zero, which > means no compression but directly memory copy. This fix will go in next pull request. Thanks.