linux-kernel - Re: [PATCH 0/9] TTY: memory leaks patchset

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: <20121116012127.GA12364@kroah.com>
Date:	Thu, 15 Nov 2012 17:21:27 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Jiri Slaby <jslaby@...e.cz>, alan@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/9] TTY: memory leaks patchset

On Thu, Nov 15, 2012 at 10:42:54AM +0000, Alan Cox wrote:
> > This series should go upstream regardless "TTY: move tty buffers to
> > tty_port" if we decide to revert that commit due to the reported
> > warnings I cannot reproduce and neither catch the root cause.
> 
> They seem to be warnings only and very obscure cases. I'd favour that
> patch not being reverted simply because the only way we'll find a pattern
> is by a lot more reports - and it doesn't seem to be anything but an
> annoying log splat.

I agree, it should stay to help catch any further problems that haven't
been fixed up yet.

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/