linux-kernel - Re: [BUG] isicom.c sleeping function called from invalid context

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:	Wed, 7 Oct 2009 14:31:32 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Alexander Strakh <strakh@...ras.ru>
Cc:	Jiri Slaby <jirislaby@...il.com>,
	Linux Kernlel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] isicom.c sleeping function called from invalid context

On Wed, 7 Oct 2009 17:15:14 +0000
Alexander Strakh <strakh@...ras.ru> wrote:

> 	KERNEL_VERSION: 2.6.31
> 	DESCRIBE:
> Driver drivers/char/isicom.c might sleep in atomic  context, because it calls 
> tty_port_xmit_buf under spin_lock.
> 
> ./drivers/char/isicom.c:
> 1307 static void isicom_hangup(struct tty_struct *tty)
> 1308 {
> ...
> 1315         spin_lock_irqsave(&port->card->card_lock, flags);
> 1316         isicom_shutdown_port(port);
> ...
> 
> Path to might_sleep macro from isicom_hangup:
> 1. isicom_hangup calls spin_lock_irqsave (drivers/char/isicom.c:1315) and then 
> calls isicom_shutdown_port.
> 2. isiscom_shutdown_port calls tty_port_free_xmit_buf at 
> drivers/char/isicom.c:906
> 3. tty_port_free_xmit_buf calls mutex_lock at srivers/char/tty_port:48
> 
> Found by Linux Driver Verification Project

Diagnosis is correct. I'll take a quick look at that one
--
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/