linux-kernel - Re: [PATCH] make last_inode counter in new_inode 32-bit on kernels that offer x86 compatability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061107180705.GD29746@wohnheim.fh-wedel.de>
Date:	Tue, 7 Nov 2006 19:07:05 +0100
From:	Jörn Engel <joern@...nheim.fh-wedel.de>
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
Cc:	Jeff Layton <jlayton@...hat.com>,
	Eric Sandeen <sandeen@...hat.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] make last_inode counter in new_inode 32-bit on kernels that offer x86 compatability

On Tue, 7 November 2006 11:53:03 -0600, Dave Kleikamp wrote:
> On Tue, 2006-11-07 at 18:42 +0100, Jörn Engel wrote:
> > 
> > Jfs really surprised me.  It appears as if it just takes the number
> > returned from new_inode in some cases - unbelievable.
> 
> jfs set it in diInitInode() (pardon the uglyMixedCaps), which is called
> in several places under diAlloc().  diAlloc() is called after
> new_inode() for most inodes.  The exceptions are for special inodes,
> which also initialize i_ino in some manner.

Yes, even I see it now.  Thanks for clearing that up.

Jörn

-- 
Joern's library part 10:
http://blogs.msdn.com/David_Gristwood/archive/2004/06/24/164849.aspx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/