From: Al Viro <viro@ftp.linux.org.uk>
To: rae l <crquan@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
Date: Wed, 25 Jul 2007 07:43:18 +0100 [thread overview]
Message-ID: <20070725064318.GD27237@ftp.linux.org.uk> (raw)
In-Reply-To: <20070725063953.GC27237@ftp.linux.org.uk>
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...
prev parent reply other threads:[~2007-07-25 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 3:48 [RFC] fs/super.c: Why alloc_super use a static variable default_op? rae l
2007-07-25 4:14 ` Al Viro
2007-07-25 4:29 ` rae l
2007-07-25 4:37 ` Al Viro
2007-07-25 5:21 ` rae l
2007-07-25 6:39 ` Al Viro
2007-07-25 6:43 ` Al Viro [this message]
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=20070725064318.GD27237@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=crquan@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox