linux-kernel - Re: [PATCH] TTY: disable debugging warning

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

Message-ID: <20130227215548.GA28005@kroah.com>
Date:	Wed, 27 Feb 2013 13:55:48 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	Daniel Mack <zonque@...il.com>,
	Larry Finger <Larry.Finger@...inger.net>, jirislaby@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] TTY: disable debugging warning

On Wed, Feb 27, 2013 at 10:48:13PM +0100, Jiri Slaby wrote:
> On 02/27/2013 10:42 PM, Greg KH wrote:
> > On Wed, Feb 27, 2013 at 10:30:24PM +0100, Jiri Slaby wrote:
> >> We added a warning to flush_to_ldisc to report cases when it is called
> >> with a NULL tty. It was for debugging purposes and it lead to a
> >> patchset from Peter Hurley. The patchset however did not make it to
> >> 3.9, so disable the warning now to not disturb people.
> >>
> >> We can re-add it when the series is in and we are hunting for another
> >> bugs.
> >>
> >> Signed-off-by: Jiri Slaby <jslaby@...e.cz>
> >> ---
> >>  drivers/tty/tty_buffer.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > Thanks, I'll queue this up for 3.9-final, but does it also need to go
> > into 3.8?
> 
> That's a question... In 3.8 it happened too, but very seldomly. Read:
> only triggerable by trinity fuzz tester after hours of fuzzing. But
> yeah, let's disable it there too so that people won't complain.

Ok, I'll queue it up for the stable release then, 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/