linux-kernel - Re: WARNING: at drivers/tty/tty_buffer.c:476 flush_to

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 19 Jan 2013 23:57:55 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Dave Jones <davej@...hat.com>, Jiri Slaby <jslaby@...e.cz>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ilya Zykov <ilya@...x.ru>, LKML <linux-kernel@...r.kernel.org>,
	linux-next <linux-next@...r.kernel.org>,
	linux-serial@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Jan Kara <jack@...e.cz>, "Theodore Ts'o" <tytso@....edu>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc()

On Sat, Jan 19, 2013 at 11:51 PM, Eric Sandeen <sandeen@...hat.com> wrote:
> On 1/19/13 4:44 PM, Sedat Dilek wrote:
>> 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!
>
> oh, excellent ;)
>
> Helped what, exactly?
>

Fixed a call-trace which I could reproduce running pm_test/freezer
(see [1] "[C.1] TRY TO FORCE THE CALL-TRACE").

- Sedat -

[1] http://marc.info/?l=linux-kernel&m=135862010419101&w=2

>>
 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
>
> Hum, I would not have expected this to *matter*, I thought it was just a perf
> optimization.  Hm.  What do you think it fixed, exactly?
>
> (sorry, have not followed that thread, busy elsewhere ATM)
>
> -eric
>
>> 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/
>>
>
--
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/