mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Greg Kroah-Hartman <greg@kroah.com>,
	Chris Wright <chris@wirex.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add SELinux module to 2.5.74-bk1
Date: Tue, 8 Jul 2003 23:50:23 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0307082337350.8438-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <20030708123304.A17486@infradead.org>

On Tue, 8 Jul 2003, Christoph Hellwig wrote:

> We use this callbacks in a bunch opf places, maybe add hash_value_t
> and keycmp_t typedefs for them to avoid typing the prototypes all
> the time?

I think this is a good idea in general, but am not sure if others agree.

> > +	p = kmalloc(sizeof(*p), GFP_KERNEL);
> 
> Pass the GFP_ mask down to hashtab_create() maybe?

Would someone need to allocate a hashtab in interrupt context?

> > +		if (prev) {
> > +			newnode->next = prev->next;
> > +			prev->next = newnode;
> 
> Use hlists?

They're overkill for this, I think.

> > +config HASHTAB
> > +	tristate "Generic hash table support"
> 
> Should this really be a user option or rather implicitly selected
> by it's users?

As with the crc32 module, we don't know if any out of tree modules will 
need to use it.

(The rest of the suggestions I agree with).

> > + -fno-strict-aliasing -fno-common -g
> 
> accident?

Yes.

Thanks for the feedback.


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



      reply	other threads:[~2003-07-08 13:39 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
2003-07-08 11:33     ` Christoph Hellwig
2003-07-08 13:50       ` James Morris [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=Mutt.LNX.4.44.0307082337350.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®