Re: [PATCH] ISAPNP: don't unlock isapnp_cfg_mutex unless we've locked it first

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

 



On Tue, 2 Mar 2010, Bjorn Helgaas wrote:


If isapnp_cfg_begin() fails, it returns without locking isapnp_cfg_mutex.
Previously, we always unlocked the mutex, even if we haven't locked it
first.

This patch checks the isapnp_cfg_begin() return value so we can just
exit and avoid this locking error.

Found by the Linux Device Drivers Verification Project and reported by
Alexander Strakh <strakh@xxxxxxxxx>.

Signed-off-by: Bjorn Helgaas <bjorn.helgaas@xxxxxx>

Acked-by: Jaroslav Kysela <perex@xxxxxxxx>

					Jaroslav

-----
Jaroslav Kysela <perex@xxxxxxxx>
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux