mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, <jgarzik@pobox.com>,
	<sds@epoch.ncsc.mil>, <torvalds@osdl.org>,
	<viro@parcelfarce.linux.theplanet.co.uk>, <hch@infradead.org>,
	<greg@kroah.com>, <chris@wirex.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add SELinux module to 2.5.74-bk1
Date: Wed, 9 Jul 2003 01:00:00 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0307090059020.8438-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <1057671907.4352.13.camel@dhcp22.swansea.linux.org.uk>

On 8 Jul 2003, Alan Cox wrote:

> On Maw, 2003-07-08 at 11:09, Andrew Morton wrote:
> > Comparing the complexity (size) of this code with the q-n-d hash tables
> > which are currently used one does wonder how useful it all will be.  The
> > additional indirections are not needed with q-n-d hashes.
> 
> Are these new hashes immune to deliberate attack (witness the network
> routing hash paper)

This is just hash table management code, hash functions are supplied by 
the caller (e.g. they could use jhash).


- James
-- 
James Morris
<jmorris@intercode.com.au>


  reply	other threads:[~2003-07-08 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 17:44 Stephen Smalley
2003-07-03 17:51 ` Jeff Garzik
2003-07-03 17:55   ` Chris Wright
2003-07-03 17:56   ` Greg KH
2003-07-03 18:05   ` Stephen Smalley
2003-07-04 15:41     ` Jeff Garzik
2003-07-08  9:49   ` James Morris
2003-07-08 10:09     ` Andrew Morton
2003-07-08 13:20       ` James Morris
2003-07-08 13:45       ` Alan Cox
2003-07-08 15:00         ` James Morris [this message]
2003-07-08 11:33     ` Christoph Hellwig
2003-07-08 13:50       ` James Morris

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=Mutt.LNX.4.44.0307090059020.8438-100000@excalibur.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chris@wirex.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    --cc=torvalds@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

all inboxes | Powered by JetHome®