Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Subject: Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
From: Davidlohr Bueso <dave@xxxxxxxxxxxx>
Date: Wed, 1 May 2019 12:22:34 -0700
Cc: Waiman Long <longman@xxxxxxxxxx>, Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>, linux-rt-users <linux-rt-users@xxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>, Clark Williams <williams@xxxxxxxxxx>, Juri Lelli <juri.lelli@xxxxxxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx>, jack@xxxxxxxx
In-reply-to: <20190501185400.GQ7905@worktop.programming.kicks-ass.net>
References: <20190326093421.GA29508@localhost.localdomain> <20190419085627.GI4742@localhost.localdomain> <20190430125130.uw7mhdnsoqr2v3gf@linutronix.de> <20190430132811.GB2589@hirez.programming.kicks-ass.net> <20190501170953.GB2650@hirez.programming.kicks-ass.net> <ce854251-139e-15f1-2ac5-b66a27f8284c@redhat.com> <20190501185400.GQ7905@worktop.programming.kicks-ass.net>
User-agent: NeoMutt/20180323

On Wed, 01 May 2019, Peter Zijlstra wrote:

Nah, the percpu_rwsem abuse by the freezer is atrocious, we really
should not encourage that. Also, it completely wrecks -RT.

Hence the proposed patch.


Is this patch (and removing rcuwait) only intended for rt?

Thanks,
Davidlohr

Follow-Ups:
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Peter Zijlstra

References:
- [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Juri Lelli
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Juri Lelli
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Sebastian Andrzej Siewior
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Peter Zijlstra
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Peter Zijlstra
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Waiman Long
- Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
  - From: Peter Zijlstra

Prev by Date: Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
Next by Date: Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
Previous by thread: Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
Next by thread: Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16)
Index(es):
- Date
- Thread

[Index of Archives] [RT Stable] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Video 4 Linux] [Device Mapper]