linux-kernel - Re: BUG mutex_unlock without mutex_lock in drivers/pnp/isapnp/core.c

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] [day] [month] [year] [list]

Message-Id: <201003021534.27001.bjorn.helgaas@hp.com>
Date:	Tue, 2 Mar 2010 15:34:26 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Alexander Strakh <strakh@...ras.ru>
Cc:	Jaroslav Kysela <perex@...ex.cz>, Adam Belay <abelay@....edu>,
	linux-kernel@...r.kernel.org
Subject: Re: BUG mutex_unlock without mutex_lock in drivers/pnp/isapnp/core.c

On Monday 01 March 2010 08:59:40 am Alexander Strakh wrote:
> 	KERNEL_VERSION: 2.6.33
> 	SUBJECT: mutex_unlock without mutex_lock
> 	DESCRIBE:
> 	In drivers/pnp/isapnp/core.c in function isapnp_get_resources:
> 
> ...
> 4. isapnp_cfg_end in line  886 calls mutex_unlock on &isapnp_cfg_mutex without 
> mutex_lock (it was not locked in function isapnp_cfg_begin because of -
> EINVAL).

Looks like a bug to me.  I'll send a patch.

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