All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: russell@coker.com.au, Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: Lukas Lueg <lukas.lueg@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Carefully crafted BTRFS-image causes kernel to crash
Date: Tue, 21 Apr 2015 07:44:12 -0400	[thread overview]
Message-ID: <5536380C.9080102@gmail.com> (raw)
In-Reply-To: <201504211938.35080.russell@coker.com.au>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On 2015-04-21 05:38, Russell Coker wrote:
> On Tue, 21 Apr 2015, Qu Wenruo <quwenruo@cn.fujitsu.com> 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.
>
And that kind of reaction is why ReiserFS isn't taken very seriously in 
an enterprise environment.

Just because something shouldn't be possible in a 'real world' 
environment, doesn't mean it won't happen; never underestimate the 
ability of hardware to fail in new and unexpected ways, or the ability 
of administrators to make stupid mistakes.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]

  reply	other threads:[~2015-04-21 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 23:04 Carefully crafted BTRFS-image causes kernel to crash Lukas Lueg
2015-04-21  3:16 ` Qu Wenruo
2015-04-21  9:38   ` Russell Coker
2015-04-21 11:44     ` Austin S Hemmelgarn [this message]
2016-08-29 17:11       ` David Sterba
2015-04-21 15:17   ` Zygo Blaxell
2015-04-22  0:28     ` Qu Wenruo
2015-04-29 19:50       ` Lukas Lueg
2015-04-30  6:45         ` Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5536380C.9080102@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lukas.lueg@gmail.com \
    --cc=quwenruo@cn.fujitsu.com \
    --cc=russell@coker.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.