From: Sedat Dilek <sedat.dilek@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ilya Zykov <ilya@ilyx.ru>, LKML <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
linux-serial@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>, Jan Kara <jack@suse.cz>,
Eric Sandeen <sandeen@redhat.com>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc()
Date: Sat, 19 Jan 2013 23:44:42 +0100 [thread overview]
Message-ID: <CA+icZUV2Fj4wtObY94s3h5=24dOhcxSuVUNv-qtRXAU5Hi-p1w@mail.gmail.com> (raw)
Hi Dave,
I suspected after initial testing a problem in TTY and applied two patches.
After more testing the root cause was a problem in JBD2.
A patch from Eric helped!
Follow the thread in [1] for more details.
If you are on Linux-Next (next-20130118) you need the following three patches.
Ilya Zykov (2):
tty: Correct tty buffer flush.
tty: Add driver unthrottle in ioctl(...,TCFLSH,..).
Eric Sandeen (1):
jbd2: don't wake kjournald unnecessarily
Hope this helps you.
Regards,
- Sedat -
[0] http://marc.info/?t=135862023700004&r=1&w=2
[1] http://marc.info/?l=linux-serial&m=135860500714909&w=2
[2] http://git.kernel.org/?p=linux/kernel/git/gregkh/tty.git;a=commitdiff;h=a1bf9584429d61b7096f93ae09325e1ba538e9e8
[3] http://patchwork.ozlabs.org/patch/207237/
next reply other threads:[~2013-01-19 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 22:44 Sedat Dilek [this message]
2013-01-19 22:51 ` WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc() Eric Sandeen
2013-01-19 22:57 ` Sedat Dilek
2013-01-20 0:14 ` Sedat Dilek
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='CA+icZUV2Fj4wtObY94s3h5=24dOhcxSuVUNv-qtRXAU5Hi-p1w@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilya@ilyx.ru \
--cc=jack@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).