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, 20 Dec 2012 12:13:07 +0000
From:	"Xiao, Jin" <>
To:	'Alan Cox' <>
CC:	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"Douglas, William" <>,
	"" <>,
	"" <>,
	"" <>,
	"Pillet, VincentX" <>
Subject: RE: [PATCH] n_gsm.c: add tx_lock in gsm_send


Thanks. But the comment makes me confused. As we see, gsm->output is called by gsm_data_kick too, and it's in the tx_lock...

Best regards,
Jin Xiao

> From: xiaojin <>
> Date: Wed, 19 Dec 2012 11:53:43 +0800
> Subject: [PATCH] n_gsm.c: add tx_lock in gsm_send
> All the call to gsm->output should be in the tx_lock, that could avoid 
> potential race from MUX level. But we have no tx_lock in gsm_send.
> This patch is to add tx_lock in gsm_send.

gsm->output calls the transmit method of the underlying tty driver. We
can't do that with interrupts off as some drivers expect to be able to sleep in their output paths.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists