From: David Sterba <dsterba@suse.cz>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] Btrfs: improve inode hash function/inode lookup
Date: Tue, 22 Oct 2013 01:21:07 +0200 [thread overview]
Message-ID: <20131021232107.GS1032@suse.cz> (raw)
In-Reply-To: <CAL3q7H6o3auNremGh8X0oFF_OcVuwpSxsOrAKDBmtx+d4eLxAQ@mail.gmail.com>
On Fri, Oct 11, 2013 at 06:20:16PM +0100, Filipe David Manana wrote:
> Good point David. However it would be a rather radical behaviour change imho.
A radical step to prevent this practictly impossible but nasty bug to
happen :)
> I think it should be a separate change if there are no objections
> against such change.
It is a separate change that makes your patch obsolete.
david
next prev parent reply other threads:[~2013-10-21 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 20:53 [PATCH] Btrfs: improve inode hash function/inode lookup Filipe David Borba Manana
2013-10-06 21:22 ` [PATCH v2] " Filipe David Borba Manana
2013-10-11 11:42 ` David Sterba
2013-10-11 17:20 ` Filipe David Manana
2013-10-21 23:21 ` David Sterba [this message]
2013-10-21 23:27 ` Filipe David Manana
2013-10-22 17:04 ` David Sterba
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=20131021232107.GS1032@suse.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).