From: Michael Ellerman <michael@ellerman.id.au>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: WARNING: at drivers/tty/tty_buffer.c:476 (tty is NULL)
Date: Tue, 12 Feb 2013 17:41:21 +1100 [thread overview]
Message-ID: <20130212064121.GA19354@concordia> (raw)
In-Reply-To: <1360637638.4415.13.camel@thor.lan>
On Mon, Feb 11, 2013 at 09:53:58PM -0500, Peter Hurley wrote:
> On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> > > 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 :)
Should have tried harder against next, git-am is very picky.
So running next-20130211, 20 runs of trinity followed by ctrl-c, I saw
the warning 12 times. Back trace is basically always:
Call Trace:
[c00000027a1efb20] [c000000000467b74] .flush_to_ldisc+0x244/0x250 (unreliable)
[c00000027a1efbd0] [c00000000009ea7c] .process_one_work+0x1bc/0x4f0
[c00000027a1efc70] [c00000000009f2e0] .worker_thread+0x180/0x4b0
[c00000027a1efd30] [c0000000000a6c3c] .kthread+0xec/0x100
[c00000027a1efe30] [c000000000009f64] .ret_from_kernel_thread+0x64/0x80
Running next-20130211 + "ldisc fixes", 20 runs of trinity followed by ctrl-c,
I saw the warning _0_ times.
Insert standard comment about testing only proving the presence of bugs not
their absence :)
So it looks promising.
cheers
next prev parent reply other threads:[~2013-02-12 6:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 15:37 WARNING: at drivers/tty/tty_buffer.c:476 (tty is NULL) Dave Jones
2013-01-18 20:53 ` Dave Jones
2013-01-18 21:07 ` Greg Kroah-Hartman
2013-01-19 21:00 ` Jiri Slaby
2013-01-30 18:33 ` Peter Hurley
2013-02-11 2:44 ` Michael Ellerman
2013-02-11 14:42 ` Peter Hurley
2013-02-12 2:00 ` Michael Ellerman
2013-02-12 2:53 ` Peter Hurley
2013-02-12 6:41 ` Michael Ellerman [this message]
2013-02-12 11:34 ` Peter Hurley
2013-02-17 6:26 ` Shawn Guo
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=20130212064121.GA19354@concordia \
--to=michael@ellerman.id.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.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