Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1626127
| From | Laurent Dufour <ldufour@linux.vnet.ibm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC 2/4] Deactivate mmap_sem assert |
| Date | 2017-04-19 15:50 +0200 |
| Message-ID | <txY9B-43H-47@gated-at.bofh.it> (permalink) |
| References | <txWKu-3m5-15@gated-at.bofh.it> <txWKu-3m5-13@gated-at.bofh.it> <txX3Q-3sb-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 19/04/2017 14:30, Peter Zijlstra wrote: > 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? I didn't explain that very well.. When using a range lock we can't check that the lock is simply held, but if the range we are interesting on is locked or not. As I mentioned this patch will have to be reverted / reviewed once the range lock is providing dedicated APIs, but some check might be difficult to adapt to a range.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC 2/4] Deactivate mmap_sem assert Laurent Dufour <ldufour@linux.vnet.ibm.com> - 2017-04-19 14:20 +0200
Re: [RFC 2/4] Deactivate mmap_sem assert Peter Zijlstra <peterz@infradead.org> - 2017-04-19 14:40 +0200
Re: [RFC 2/4] Deactivate mmap_sem assert Laurent Dufour <ldufour@linux.vnet.ibm.com> - 2017-04-19 15:50 +0200
Re: [RFC 2/4] Deactivate mmap_sem assert Peter Zijlstra <peterz@infradead.org> - 2017-04-19 16:00 +0200
csiph-web