linux-kernel - Re: [RFC] fs/super.c: Why alloc_super use a static variable default

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] [day] [month] [year] [list]

Message-ID: <20070725064318.GD27237@ftp.linux.org.uk>
Date:	Wed, 25 Jul 2007 07:43:18 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	rae l <crquan@...il.com>
Cc:	Alexander Viro <viro@...iv.linux.org.uk>,
	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?

On Wed, Jul 25, 2007 at 07:39:53AM +0100, Al Viro wrote:

> For superblocks and inodes that is different - if we go looking for a method,
> we *are* going to hit the method table anyway; it's not going to be NULL in
> anything resembling a normal case.  So having the pointer to table initialized

"it" == "pointer to method table", of course.  Pointers _in_ method table
might very well be NULL...
-
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/