Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1534373
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [patch 0/4] rtmutex: Plug unlock vs. requeue race |
| Date | 2016-12-01 19:40 +0100 |
| Message-ID | <sJEqZ-8du-9@gated-at.bofh.it> (permalink) |
| References | <sJkiB-2NQ-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Nov 30, 2016 at 09:04:40PM -0000, Thomas Gleixner wrote: > The following series plugs a subtle race and robustifies the code > further. Aside of that it adds commentry about lockless operations and > removes a confusing extra define. Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[patch 0/4] rtmutex: Plug unlock vs. requeue race Thomas Gleixner <tglx@linutronix.de> - 2016-11-30 22:10 +0100
[patch 4/4] rtmutex: Explain locking rules for rt_mutex_proxy_unlock()/init_proxy_locked() Thomas Gleixner <tglx@linutronix.de> - 2016-11-30 22:10 +0100
[tip:locking/core] locking/rtmutex: Explain locking rules for rt_mutex_proxy_unlock()/init_proxy_locked() tip-bot for Thomas Gleixner <tipbot@zytor.com> - 2016-12-02 12:20 +0100
[patch 2/4] rtmutex: Use READ_ONCE() in rt_mutex_owner() Thomas Gleixner <tglx@linutronix.de> - 2016-11-30 22:10 +0100
[tip:locking/core] locking/rtmutex: Use READ_ONCE() in rt_mutex_owner() tip-bot for Thomas Gleixner <tipbot@zytor.com> - 2016-12-02 11:50 +0100
Re: [patch 0/4] rtmutex: Plug unlock vs. requeue race Peter Zijlstra <peterz@infradead.org> - 2016-12-01 19:40 +0100
csiph-web