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
| ||
|
Date: Wed, 30 Jan 2013 10:55:00 +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 06:12, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote: > It doesn't apply cleanly to the linux-next tree, can you refresh this > and resend it so that I can apply it? If you want it backported to the > stable kernel releases, we can only do that after it gets into Linus's > tree, see the file, Documentation/stable_kernel_rules.txt for details > about this. I've reapplied the patch to linux-next and submitted it just now. Is there anything additionally that needs to be done to merge this back to stable after this patch is applied? I also changed the additional check conditions by changing them into if (dlci->state == DLCI_CLOSED) During testing I've found that there can be a case where gsmtty_ioctl was called while it was still in the state DLCI_OPENING and this is not a problematic case. Therefore I changed the check from the original patch to the one shown in the new one. -- 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/
Powered by blists - more mailing lists