Re: [PATCH 4/7] fs: break the file_list_lock for sb->s_files

* Christoph Hellwig <[email protected]> wrote:

> > > NACK.  Please don't start using lockdep internals in core code.
> > 
> > what do you mean by that?
> 
> struct lock_list is an lockdep implementation detail and should not 
> leak out and be used anywhere else.  [...]

no, it is not. It is a new data type.

	Ingo
-
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:
  • [PATCH 0/7] breaking the global file_list_lock
    • From: Peter Zijlstra <[email protected]>
  • [PATCH 4/7] fs: break the file_list_lock for sb->s_files
    • From: Peter Zijlstra <[email protected]>
  • Re: [PATCH 4/7] fs: break the file_list_lock for sb->s_files
    • From: Christoph Hellwig <[email protected]>
  • Re: [PATCH 4/7] fs: break the file_list_lock for sb->s_files
    • From: Ingo Molnar <[email protected]>
  • Re: [PATCH 4/7] fs: break the file_list_lock for sb->s_files
    • From: Christoph Hellwig <[email protected]>

• Prev by Date: Re: Bugfixes: PCI devices get assigned redundant IRQs
• Next by Date: Re: [PATCH] mm: remove global locks from mm/highmem.c
• Previous by thread: Re: [PATCH 4/7] fs: break the file_list_lock for sb->s_files
• Next by thread: Re: [PATCH 4/7] fs: break the file_list_lock for sb->s_files
• 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]