All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@caldera.de>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: acme@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [CFT] [JANITORIAL] Unbork fs.h
Date: Thu, 3 Jan 2002 19:35:38 +0100	[thread overview]
Message-ID: <20020103193537.A13386@caldera.de> (raw)
In-Reply-To: <200201031545.g03Fjtj11546@ns.caldera.de> <E16MAbL-00018W-00@starship.berlin>
In-Reply-To: <E16MAbL-00018W-00@starship.berlin>; from phillips@bonn-fries.net on Thu, Jan 03, 2002 at 05:20:12PM +0100

On Thu, Jan 03, 2002 at 05:20:12PM +0100, Daniel Phillips wrote:
> On January 3, 2002 04:45 pm, Christoph Hellwig wrote:
> > In article <E16M7Gz-00015E-00@starship.berlin> you wrote:
> > > -	inode = get_empty_inode();
> > > +	inode = get_empty_inode(sb);
> > 
> > How about killing get_empty_inode completly and using new_inode() instead?
> > There should be no regularly allocated inode without a superblock.
> 
> There are: sock_alloc rd_load_image.  However that's a nit because the new, 
> improved get_empty_inode understands the concept of null sb.

get_empty_inode is hopefully going to die in the current, non-static version.

> (Another thing 
> we could do is require every inode to have a superblock - that's probably 
> where it will go in time.)

Any inode that gets into the icache already has and superblock.
If any other are left they really should use a different allocator.

> We put this inside get_empty_inode:
> 
> 	if (inode) {
> 		inode->i_dev = sb->s_dev;
> 		inode->i_blkbits = sb->s_blocksize_bits;
> 	}
> 
> then rename it new_inode.  But this is outside of the scope of the fs.h work 
> I'm doing, don't you think?

Rename your current get_empty_inode to __get_empty_inode and mark it
static.  Add a new get_empty_inode that calls __get_empty_inode(NULL) or
better let it die.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  parent reply	other threads:[~2002-01-03 18:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 12:47 [CFT] [JANITORIAL] Unbork fs.h Daniel Phillips
2002-01-03 14:03 ` Daniel Phillips
2002-01-03 15:45 ` Christoph Hellwig
2002-01-03 16:20   ` Daniel Phillips
2002-01-03 16:47     ` Alexander Viro
2002-01-03 17:25       ` Daniel Phillips
2002-01-03 18:25     ` Daniel Phillips
2002-01-03 18:35     ` Christoph Hellwig [this message]
2002-01-03 16:45   ` Alexander Viro
2002-01-03 18:04     ` Daniel Phillips
2002-01-03 16:05 ` Ion Badulescu
2002-01-03 16:34   ` Daniel Phillips
2002-01-03 16:28     ` Martin Dalecki
2002-01-03 16:45       ` Arnaldo Carvalho de Melo
2002-01-03 16:36     ` Arnaldo Carvalho de Melo
2002-01-03 17:05       ` Daniel Phillips
2002-01-03 17:07         ` Arnaldo Carvalho de Melo
2002-01-03 19:36           ` Andreas Dilger
2002-01-04  7:05             ` Daniel Phillips
2002-01-04  8:59               ` Andreas Dilger
2002-01-04 10:02                 ` Jeff Garzik
2002-01-03 23:25         ` J.A. Magallon
2002-01-04  1:44           ` Daniel Phillips
2002-01-04 14:52             ` J.A. Magallon
2002-01-03 18:53       ` Daniel Phillips
2002-01-03 20:31     ` Ion Badulescu
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04 15:16 Andries.Brouwer
2002-01-04 22:20 ` Andreas Dilger
2002-01-04 23:33   ` Daniel Phillips
2002-01-04 16:45 Bryan Henderson
2002-01-04 22:15 ` Andreas Dilger
2002-01-05  1:07 Bryan Henderson

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=20020103193537.A13386@caldera.de \
    --to=hch@caldera.de \
    --cc=acme@conectiva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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.