linux-kernel - Re: [PATCH] tty: annotate tty

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]

Date:	Thu, 31 May 2012 13:55:54 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc:	Jiri Kosina <jkosina@...e.cz>, Alan Cox <alan@...ux.intel.com>,
	Jiri Slaby <jslaby@...e.cz>, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] tty: annotate tty_lock() for lockdep

On Thu, 2012-05-31 at 17:01 +0530, Srikar Dronamraju wrote:
> Hi Jiri, 
> 
> 
> 
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > 3.4.0-08218-gb48b2c3 #7 Not tainted
> > ---------------------------------------------
> > blogd/279 is trying to acquire lock:
> >  (&tty->legacy_mutex){+.+.+.}, at: [<ffffffff8150f51e>] tty_lock+0x3e/0x90
> > 
> > but task is already holding lock:
> >  (&tty->legacy_mutex){+.+.+.}, at: [<ffffffff8150f51e>] tty_lock+0x3e/0x90
> > 
> > other info that might help us debug this:
> >  Possible unsafe locking scenario:
> > 
> >        CPU0
> >        ----
> >   lock(&tty->legacy_mutex);
> >   lock(&tty->legacy_mutex);
> > 
> >  *** DEADLOCK ***
> > 
> 
> I saw a similar problem and applied your patch, but that doesnt seem to
> help me.

I was not aware of Jiri patch

Try this one instead :

https://lkml.org/lkml/2012/5/31/125



--
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/