linux-kernel - Re: [PATCH 18/18] fs: do not assign default i_ino in new

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: <20101016163035.GC20086@infradead.org>
Date:	Sat, 16 Oct 2010 12:30:35 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Nick Piggin <npiggin@...nel.dk>
Cc:	Dave Chinner <david@...morbit.com>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 18/18] fs: do not assign default i_ino in new_inode

On Sat, Oct 16, 2010 at 06:57:28PM +1100, Nick Piggin wrote:
> My patch for this reduces churn by just adding a new function instead.
> The last_ino allocator is really fast now, so IMO it was not worth
> the churn to go through filesystems; just let them do it.

See the last comment on this.  Allocating an inode and assigning a badly
made up ino for a handfull synthetic filesystems are very different
things.  Mixing them up in one function always was a bad idea.

--
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/