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] [thread-next>] [day] [month] [year] [list]

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

On Wed, Jan 30, 2013 at 10:55:00AM +0100, Dirkjan Bussink wrote:
> 
> 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? 

You need to add a "cc: stable@...r.kernel.org" line to the
signed-off-by: area.  I'll do it to the patch when I apply it.

I found the problem, your email client stripped out the trailing spaces
of the patch, which kept it from being applied as it wasn't a valid
patch.  I've edited it by hand this time, but next time please fix your
email client.

thanks,

greg k-h
--
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/