lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 30 Apr 2019 16:53:43 +0200 From: Oleg Nesterov <oleg@...hat.com> To: Peter Zijlstra <peterz@...radead.org> Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>, linux-rt-users <linux-rt-users@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Daniel Bristot de Oliveira <bristot@...hat.com>, Clark Williams <williams@...hat.com>, Juri Lelli <juri.lelli@...hat.com>, jack@...e.com Subject: Re: [RT WARNING] DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) with fsfreeze (4.19.25-rt16) On 04/30, Peter Zijlstra wrote: > > On Tue, Apr 30, 2019 at 04:42:53PM +0200, Oleg Nesterov wrote: > > I have cloned linux-rt-devel.git > > > > If I understand correctly, in rt rw_semaphore is actually defined in rwsem_rt.h > > so percpu_rwsem_acquire() should probably do > > > > sem->rw_sem.rtmutex.owner = current; > > That'll screw the PI chain (if there is one), right? Yes, I have already realized this can't work after I glanced at this code, thanks. Oleg.
Powered by blists - more mailing lists