On Wed, Apr 19, 2017 at 02:18:25PM +0200, Laurent Dufour wrote: > When mmap_sem will be moved to a range lock, some assertion done in > the code are no more valid, like the one ensuring mmap_sem is held. >
Why are they no longer valid?
- [RFC 0/4] Replace mmap_sem by a range lock Laurent Dufour
- [RFC 2/4] Deactivate mmap_sem assert Laurent Dufour
- Re: [RFC 2/4] Deactivate mmap_sem assert Peter Zijlstra
- Re: [RFC 2/4] Deactivate mmap_sem assert Laurent Dufour
- Re: [RFC 2/4] Deactivate mmap_sem assert Peter Zijlstra
- [RFC 3/4] Remove nest locking operation with mmap_sem Laurent Dufour
- [RFC 1/4] Add additional range parameter to GUP() and ... Laurent Dufour
- Re: [RFC 0/4] Replace mmap_sem by a range lock Matthew Wilcox
- Re: [RFC 0/4] Replace mmap_sem by a range lock Laurent Dufour
- Re: [RFC 4/4] Change mmap_sem to range lock Peter Zijlstra
- Re: [RFC 4/4] Change mmap_sem to range lock Laurent Dufour
- Re: [RFC 4/4] Change mmap_sem to range lock Andi Kleen
