linux-kernel - Re: [PATCH] tty: Prevent deadlock in n

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]

Date:	Wed, 30 Jan 2013 11:46:12 +0100
From:	Dirkjan Bussink <dirkjan.bussink@...ap.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tty: Prevent deadlock in n_gsm driver


On 30 Jan 2013, at 11:10, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:

> This patch breaks the build in the tty-next tree:
> 
> drivers/tty/n_gsm.c: In function ‘gsm_dlci_release’:
> drivers/tty/n_gsm.c:1713:3: error: too few arguments to function ‘tty_unlock’
> In file included from drivers/tty/n_gsm.c:44:0:
> include/linux/tty.h:596:24: note: declared here
> drivers/tty/n_gsm.c:1715:3: error: too few arguments to function ‘tty_lock’
> In file included from drivers/tty/n_gsm.c:44:0:
> include/linux/tty.h:595:24: note: declared here
> 
> Can you fix this up (get it to build on the linux-next tree) and resend
> it?

I've resent it with the proper changes. I also tried to ensure that the patch
wasn't mangled this time, so that should be good as well now. Please let me
know if this is still problematic, I've used mutt and -H to send the patch
created with git format-patch. 

-- 
Regards,

Dirkjan Bussink

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