From: Jeff Layton <jlayton@redhat.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via pointer conversion)
Date: Fri, 17 Nov 2006 10:06:55 -0500 [thread overview]
Message-ID: <1163776015.13410.71.camel@dantu.rdu.redhat.com> (raw)
In-Reply-To: <1163775685.17280.13.camel@kleikamp.austin.ibm.com>
On Fri, 2006-11-17 at 09:01 -0600, Dave Kleikamp wrote:
> Wouldn't you only be able to only crack a few of the low-order bits due
> to a cluster of inodes being sequential? I don't think you'd be able
> crack enough of it to be useful. You may be able to determine where
> some inodes are relative to others, but I don't think you'd be able to
> point the their location in memory. I don't know anything about crypto,
> so I could be wrong.
>
On a 64-bit kernel, that would be the case. On a 32-bit kernel, there
are no high order bits to chop off, so this would effectively give you
the address.
-- Jeff
next prev parent reply other threads:[~2006-11-17 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 13:43 [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via pointer conversion) Jeff Layton
2006-11-17 13:50 ` Matthew Wilcox
2006-11-17 14:14 ` Jörn Engel
2006-11-17 14:24 ` Jeff Layton
2006-11-17 14:21 ` Jeff Layton
2006-11-17 16:31 ` Jeff Layton
2006-11-17 14:24 ` Matthew Wilcox
2006-11-17 14:48 ` Jeff Layton
2006-11-17 15:01 ` Dave Kleikamp
2006-11-17 15:06 ` Jeff Layton [this message]
2006-11-17 15:26 ` Dave Kleikamp
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=1163776015.13410.71.camel@dantu.rdu.redhat.com \
--to=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=shaggy@linux.vnet.ibm.com \
/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).