Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1685457
| From | Byungchul Park <byungchul.park@lge.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite |
| Date | 2017-07-12 04:10 +0200 |
| Message-ID | <u2fgd-1TD-11@gated-at.bofh.it> (permalink) |
| References | <tKAsO-ma-13@gated-at.bofh.it> <tKAsO-ma-29@gated-at.bofh.it> <u263f-4Bc-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Jul 11, 2017 at 06:12:32PM +0200, Peter Zijlstra wrote: > > ARGH!!! please, if there are known holes in patches, put a comment in. The fourth of the last change log is the comment, but it was not enough. I will try to add more comment in that case. > I now had to independently discover this problem during review of the > last patch. > ... > > Right, like I wrote in the comment; I don't think you need quite this > much. > > The problem only happens if you rewind more than MAX_XHLOCKS_NR; > although I realize it can be an accumulative rewind, which makes it > slightly more tricky. > > We can either make the rewind more expensive and make xhlock_valid() > false for each rewound entry; or we can keep the max_idx and account Does max_idx mean the 'original position - 1'? > from there. If we rewind >= MAX_XHLOCKS_NR from the max_idx we need to > invalidate the entire state, which we can do by invaliding Could you explain what the entire state is? > xhlock_valid() or by re-introduction of the hist_gen_id. When we What does the re-introduction of the hist_gen_id mean? > invalidate the entire state, we can also clear the max_idx.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Peter Zijlstra <peterz@infradead.org> - 2017-07-11 18:20 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-12 04:10 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Peter Zijlstra <peterz@infradead.org> - 2017-07-12 10:00 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-13 04:10 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Peter Zijlstra <peterz@infradead.org> - 2017-07-13 10:20 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-13 11:00 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Peter Zijlstra <peterz@infradead.org> - 2017-07-13 12:00 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-13 12:20 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Peter Zijlstra <peterz@infradead.org> - 2017-07-13 12:30 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Peter Zijlstra <peterz@infradead.org> - 2017-07-13 13:20 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <max.byungchul.park@gmail.com> - 2017-07-13 13:30 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-14 03:50 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-14 08:50 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <max.byungchul.park@gmail.com> - 2017-07-13 13:20 +0200
Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite Byungchul Park <byungchul.park@lge.com> - 2017-07-18 03:30 +0200
csiph-web