From: Paul Fulghum <paulkf@microgate.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Jason Baron <jbaron@redhat.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"jesper.juhl@gmail.com" <jesper.juhl@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] tty reference count fix
Date: Mon, 13 Feb 2006 18:20:24 -0600 [thread overview]
Message-ID: <43F12248.7070608@microgate.com> (raw)
In-Reply-To: <43F119FC.10900@microgate.com>
Paul Fulghum wrote:
> Your patch leaves the schedule() call at the bottom of
> the while loop between setting tty_closing and
> setting TTY_CLOSING flag.
Nevermind. After schedule() the count is reread,
so you are right. Dropping tty_sem altogether
would work.
It is a matter of where you ultimately wish to
push the locking to BKL or tty_sem.
--
Paul Fulghum
Microgate Systems, Ltd
next prev parent reply other threads:[~2006-02-14 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 20:13 [PATCH] tty reference count fix Paul Fulghum
2006-02-13 22:15 ` Jesper Juhl
2006-02-13 23:21 ` Paul Fulghum
2006-02-13 22:51 ` Jason Baron
2006-02-13 23:45 ` Paul Fulghum
2006-02-14 0:20 ` Paul Fulghum [this message]
2006-02-14 21:46 ` Arjan van de Ven
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=43F12248.7070608@microgate.com \
--to=paulkf@microgate.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jbaron@redhat.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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