From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 220-245-31-42.static.tpgi.com.au ([220.245.31.42]:43986 "EHLO smtp.sws.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750867AbbDUJir (ORCPT ); Tue, 21 Apr 2015 05:38:47 -0400 From: Russell Coker Reply-To: russell@coker.com.au To: Qu Wenruo Subject: Re: Carefully crafted BTRFS-image causes kernel to crash Date: Tue, 21 Apr 2015 19:38:34 +1000 Cc: Lukas Lueg , linux-btrfs@vger.kernel.org References: <5535C11C.2050308@cn.fujitsu.com> In-Reply-To: <5535C11C.2050308@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Message-Id: <201504211938.35080.russell@coker.com.au> Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Tue, 21 Apr 2015, Qu Wenruo wrote: > Although we may add extra check for such problem to improve robustness, > but IMHO it's not a real world problem. Some of the ReiserFS developers gave a similar reaction to some of my bug reports. ReiserFS wasn't the most robust filesystem. I think that it should be EXECTED that a kernel will have to occasionally deal with filesystem images that are created by hostile parties. Userspace crash and kernel freeze is not a suitable way of dealing with it. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/