From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
paulkf@microgate.com, akpm@osdl.org
Subject: Re: [PATCH] Ref counting for tty_struct and some locking clean up
Date: Fri, 7 Jul 2006 18:33:48 -0700 [thread overview]
Message-ID: <20060707183348.157cc272.rdunlap@xenotime.net> (raw)
In-Reply-To: <9e4733910607071737n1bd01042u92b895edaceb73db@mail.gmail.com>
On Fri, 7 Jul 2006 20:37:36 -0400 Jon Smirl wrote:
> This patch removes tty_mutex and replaces it with a ref counted
> tty_struct. A new spinlock, tty_lock, serializes tty
> creation/destruction. This code thoroughly audits everyone taking
> references to tty_struct and tracks them. I have been running it
> locally for a few days without any issues.
>
> If there is a refcount problem it will trigger a WARN_ON. If you hit
> one, defining DEBUG_TTY_REFCOUNT will provide plenty of debug info to
> help locate the missing reference. I definitely found multiple locking
> holes in the old tty_mutex code but they they look hard to hit.
>
> This is just a first step, if this code proves to be stable I'll do
> another round of cleanup. There is room for a lot more work to be
> done. Ultimately there may not even be a need for a tty refcount if
> everything is locked correctly. But that is a big step and we should
> take some smaller ones first.
>
> This is meant for mm until it gets some testing - I don't want to
> break anyone's console. If gmail wraps it let me know and I'll send
> you an attachment.
It has one wrapped line in it but does not apply cleanly to
2.6.18-rc1 or to 2.6.17-mm6. What was it diffed against?
---
~Randy
next prev parent reply other threads:[~2006-07-08 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 0:37 Jon Smirl
2006-07-08 1:33 ` Randy.Dunlap [this message]
[not found] ` <9e4733910607071833r3d2dcea0la7e26a6d0b60bd3@mail.gmail.com>
2006-07-08 1:39 ` Randy.Dunlap
2006-07-08 1:44 ` Randy.Dunlap
[not found] ` <9e4733910607071847l605c11d3xe67cae38cd54adb4@mail.gmail.com>
2006-07-08 1:52 ` Randy.Dunlap
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=20060707183348.157cc272.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
/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®