From: Chris Mason <chris.mason@fusionio.com>
To: Pascal Junod <pascal@junod.info>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [btrfs] is vulnerable to a hash-DoS attack
Date: Thu, 13 Dec 2012 15:52:08 -0500 [thread overview]
Message-ID: <20121213205208.GA27308@shiny> (raw)
In-Reply-To: <50C9D085.3020305@junod.info>
[ adding linux-btrfs ]
On Thu, Dec 13, 2012 at 05:56:37AM -0700, Pascal Junod wrote:
> Hello folk,
>
> The btrfs file system, part of the linux kernel, is vulnerable to a
> trivial hash-DoS attack. More details can be found here:
>
> http://crypto.junod.info/2012/12/13/hash-dos-and-btrfs/
Hi Pascal,
Thanks for taking the time to write this up. As far as I can tell, the
looping was actually fixed in an older kernel and I just misread our
version string in your original email.
I'll track down the commit that fixed things and send it off to the
stable series. SuSE and Fujitsu have done a number of error handling
cleanups, it should be one of those.
-chris
next prev parent reply other threads:[~2012-12-13 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 12:56 [btrfs] is vulnerable to a hash-DoS attack Pascal Junod
2012-12-13 20:52 ` Chris Mason [this message]
2012-12-13 21:34 ` David Sterba
2012-12-13 22:07 ` Chris Mason
2012-12-14 14:29 ` Chris Mason
2012-12-14 16:41 ` Pascal Junod
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=20121213205208.GA27308@shiny \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pascal@junod.info \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox