linux-kernel - Re: [PATCH 2/7] omfs: add inode routines

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: <b6c5339f0803280634u1ab1b3aare58d3794dfde2af9@mail.gmail.com>
Date:	Fri, 28 Mar 2008 09:34:56 -0400
From:	"Bob Copeland" <me@...copeland.com>
To:	"Arnd Bergmann" <arnd@...db.de>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 2/7] omfs: add inode routines

On Thu, Mar 27, 2008 at 11:42 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Thursday 27 March 2008, Bob Copeland wrote:
>  If you could avoid the i_state member in omfs_inode_info, you could get
>  rid of your own inode cache entirely. Your i_state seems to be mostly
>  write-only, why is it needed in your file system?

Err, yeah, it looks to be superfluous.  I think it's a relic from when
I once did an initialization in omfs_write_inode.

Thanks,
Bob
--
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/