linux-kernel - Re: [PATCH] kernel/locking/locktorture: fix deadlock in 'rw_lock

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1425690180.19505.68.camel@stgolabs.net>
Date:	Fri, 06 Mar 2015 17:03:00 -0800
From:	Davidlohr Bueso <dave@...olabs.net>
To:	paulmck@...ux.vnet.ibm.com
Cc:	Alexey Kodanev <alexey.kodanev@...cle.com>, josh@...htriplett.org,
	linux-kernel@...r.kernel.org, vasily.isaenko@...cle.com
Subject: Re: [PATCH] kernel/locking/locktorture: fix deadlock in
 'rw_lock_irq' type

On Fri, 2015-03-06 at 16:37 -0800, Paul E. McKenney wrote:
> On Sat, Mar 07, 2015 at 03:06:53AM +0300, Alexey Kodanev wrote:
> > torture_rwlock_read_unlock_irq() must use read_unlock_irqrestore()
> > instead of write_unlock_irqrestore().
> > 
> > Use read_unlock_irqrestore() instead of write_unlock_irqrestore().
> > 
> > Signed-off-by: Alexey Kodanev <alexey.kodanev@...cle.com>
> 
> Good catch!  If Davidlohr has no objections, I will queue this one.

Dear me, yes that looks completely borken. Thanks for the fix.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/