All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Junod <pascal@junod.info>
To: Chris Mason <chris.mason@fusionio.com>,
	Chris Mason <clmason@fusionio.com>, David Sterba <dave@jikos.cz>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [btrfs] is vulnerable to a hash-DoS attack
Date: Fri, 14 Dec 2012 17:41:52 +0100	[thread overview]
Message-ID: <50CB56D0.7010509@junod.info> (raw)
In-Reply-To: <20121214142932.GB19606@shiny>

Le 14.12.12 15:29, Chris Mason a écrit :

> Ok, I think what was happening on Pascal's machine is that we are
> returning -EOVERFLOW and sometimes aborting the transaction (which turns
> the FS readonly).
> 
> I have that fixed here.  Rename I'm reodering the rename code a little
> bit to also handle the case where there are collisions on rename.

Please tell me if I can help by explaining more about my setup.

Pascal


      reply	other threads:[~2012-12-14 16:42 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
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 [this message]

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=50CB56D0.7010509@junod.info \
    --to=pascal@junod.info \
    --cc=chris.mason@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=dave@jikos.cz \
    --cc=linux-btrfs@vger.kernel.org \
    /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.