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()
Date: Thu, 15 Oct 2009 12:47:10 +0100 [thread overview]
Message-ID: <20091015124710.502c45b8@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4AD6FB9B.5030704@cfl.rr.com>
> 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.
prev parent reply other threads:[~2009-10-15 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 10:38 Mark Hounschell
2009-10-15 11:47 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091015124710.502c45b8@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®