linux-kernel - Re: WARNING: at drivers/tty/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: <1360637638.4415.13.camel@thor.lan>
Date:	Mon, 11 Feb 2013 21:53:58 -0500
From:	Peter Hurley <peter@...leysoftware.com>
To:	Michael Ellerman <michael@...erman.id.au>
Cc:	Jiri Slaby <jslaby@...e.cz>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: WARNING: at drivers/tty/tty_buffer.c:476  (tty is NULL)

On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> Sorry I just mean I'm seeing the warning, I have no idea how.

Ok, no problem. I just got a little excited because that area of code
was hard to test adequately.

> > Can you reproduce after using the following patch series?
> > [PATCH v3 00/23] ldisc fixes
> 
> What are they against? I tried Linus' tree and linux-next but they
> didn't apply cleanly against either.

The series was generated against next-20130204. 13/23 doesn't apply
cleanly at next-20130211 because of changes since. Rebases fine
though :)

The series is currently in mid-review, so a new series won't be out
until that completes.  (Besides, next-20130211 doesn't even boot for
me.)

Regards,
Peter Hurley

--
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/