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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC] fs/super.c: Why alloc_super use a static variable default_op?
    • From: "rae l" <[email protected]>
  • Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
    • From: Al Viro <[email protected]>
  • Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
    • From: "rae l" <[email protected]>
  • Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
    • From: Al Viro <[email protected]>
  • Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
    • From: "rae l" <[email protected]>
  • Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
    • From: Al Viro <[email protected]>

• Prev by Date: make randconfig improvement
• Next by Date: Re: [patch] mm: reduce pagetable-freeing latencies
• Previous by thread: Re: [RFC] fs/super.c: Why alloc_super use a static variable default_op?
• Next by thread: [patch] oom: print points as unsigned long
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]