linux-kernel - Re: TTY: warning in tty_lock on 2.6.35+gregkh tree

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] [day] [month] [year] [list]

Message-ID: <AANLkTi=J9OpOcsGH1nGqu5O2O3TRGit3Lh=QUQL_u6Er@mail.gmail.com>
Date:	Sat, 7 Aug 2010 16:35:34 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: TTY: warning in tty_lock on 2.6.35+gregkh tree

2010/8/7 Arnd Bergmann <arnd@...db.de>:
> On Saturday 07 August 2010, Ming Lei wrote:
>> Following the ttty warning during kernel boot, seems it is for a long time
>> in gregkh's tree.
>
> The fix for this is in the bkl/core tree, meaning it doesn't show up
> in the linux-next tree.
>
> The warning by itself is harmless, so there was no strict need to
> coordinate this better. In fact, with the removal of the optional
> BKL behavior, I believe the warning is now gone from the tty
> tree as well.

Oh, I see, thanks.

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