Date: Thu, 15 Oct 2009 12:47:10 +0100
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mark Hounschell <dmarkh@cfl.rr.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
       Mark Hounschell <markh@compro.net>
Subject: Re: WARNING: at lib/kref.c:43 kref_get+0x18/0x20()
Message-ID: <20091015124710.502c45b8@lxorguk.ukuu.org.uk>
In-Reply-To: <4AD6FB9B.5030704@cfl.rr.com>
References: <4AD6FB9B.5030704@cfl.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 912
Lines: 19

> I know there have been many changes to the serial/tty stuff recently. I think
> this is not a driver but kernel issue so I thought I'd bring it up here in hope
> to find out for sure.

Its probably a combination of the two. While digi persist in keeping
their stuff out of tree its always going to lag and not get fixed in
parallel or even considered during tty reworking.

First guess would be that the driver has paths that free a tty kref but
don't take it (ie unbalanced counts) second that may be it can't cope
with the changes caused by the switches to refcounting throughout the tty
code.

One for Digi to answer given they insist on keeping it out of tree.
--
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/