public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Daniel Mack <zonque@gmail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	jirislaby@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TTY: disable debugging warning
Date: Wed, 27 Feb 2013 13:55:48 -0800	[thread overview]
Message-ID: <20130227215548.GA28005@kroah.com> (raw)
In-Reply-To: <512E7F1D.2070401@suse.cz>

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@suse.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

      reply	other threads:[~2013-02-27 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 21:30 [PATCH] TTY: disable debugging warning Jiri Slaby
2013-02-27 21:42 ` Greg KH
2013-02-27 21:48   ` Jiri Slaby
2013-02-27 21:55     ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130227215548.GA28005@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zonque@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox