linux-kernel - Re: proper tty-ldisc refcounting (was Re: WARNING at: drivers/char/tty

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: <20090804035319.GA7248@kroah.com>
Date:	Mon, 3 Aug 2009 20:53:19 -0700
From:	Greg KH <greg@...ah.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Sergey Senozhatsky <sergey.senozhatsky@...l.by>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: proper tty-ldisc refcounting (was Re: WARNING at:
 drivers/char/tty_ldisc.c)

On Mon, Aug 03, 2009 at 05:56:07PM -0700, Linus Torvalds wrote:
> 
> 
> On Tue, 4 Aug 2009, Sergey Senozhatsky wrote:
> >   
> > Works for me (SMP/non-SMP x86 builds). Great job.
> >   
> > Tested-by: Sergey Senozhatsky <sergey.senozhatsky@...l.by>
> 
> Thanks.
> 
> Greg - feel free to treat 4/2 and 5/2 any way you want. They are obvious 
> enough (no subtle issues) that I'll happily pull them into 2.6.31 too: 
> relative to the initial refcount changes (which it looks like we'll need 
> to do just to fix the regression) they are pretty safe.
> 
> But at the same time, they can equally well go into some later tree for 
> the next merge window. So whatever you want to do.

I'll queue them up for .32 as they don't fix a bug that people are
hitting from what I can tell.

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/