Date: Tue, 5 Jan 2010 00:12:05 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Breuer <mbreuer@majjas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tty_io.c  - disassociate_ctty attempted to write to tty = NULL
 question/problem?
Message-ID: <20100105001205.7e8f131b@lxorguk.ukuu.org.uk>
In-Reply-To: <4B42733D.6050704@majjas.com>
References: <4B42733D.6050704@majjas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1034
Lines: 26

> do_exit -> disassocate_ctty(1) (for tty1).
> disassociate->vhangup->do_tty_hangup
> 
> In do_tty_hangup, p->signal->tty is set to NULL, where p==current.

Perfectly reasonable so far - the current process gave up having a
controlling tty.

> On return, the aforementioned error message is generated.

>From where - the backtrace on the write to NULL tty is the important bit
here. User space interfaces cache tty in filp->private_data so its not
going to be coming from there unless there was a memory scribble which
would imply a refcounting bug - and I'd expect people to hit that
reliably.

Some kernel stuff does take a peek at p->signal->tty for direct printk
type stuff and that sounds more likely - the backtraceon the write to
NULL tty is going to provide the needed info.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/