linux-kernel - Re: tty_io.c - disassociate_ctty attempted to write to tty = NULL question/problem?

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: <20100105104746.095e5745@lxorguk.ukuu.org.uk>
Date:	Tue, 5 Jan 2010 10:47:46 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Michael Breuer <mbreuer@...jas.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: tty_io.c  - disassociate_ctty attempted to write to tty = NULL
 question/problem?

> Ok - thanks - added a WARN_ON(!tty) right after the second call to 
> get_current_tty() in disassociate_ctty()

Thsats a perfectly valid path. Its whatever is doing the write you need
to catch. Having a NULL current tty is perfectly acceptable.

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