From: Robert Love <rml@tech9.net>
To: gordo@pincoya.com
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] console close race fix resend
Date: 11 Dec 2001 01:05:18 -0500 [thread overview]
Message-ID: <1008050718.4287.11.camel@phantasy> (raw)
In-Reply-To: <20011210191630.A13679@furble>
In-Reply-To: <1008035512.4287.1.camel@phantasy> <20011210191630.A13679@furble>
On Mon, 2001-12-10 at 22:16, Gordon Oliver wrote:
> and (c) appears to still have a race... You should extract
> the value from the structure inside the lock, otherwise you
> will still race with con_close (though perhaps a smaller race)
> but since the call to acquire_console_sem() can sleep, the
> vt handle you have may be stale.
Ehh, I don't think so. Here is the whole patched function:
static void con_flush_chars(struct tty_struct *tty)
{
struct vt_struct *vt = (struct vt_struct *)tty->driver_data;
if (in_interrupt()) /* from flush_to_ldisc */
return;
pm_access(pm_con);
acquire_console_sem();
if (vt)
set_cursor(vt->vc_num);
release_console_sem();
}
When we check vt, it isn't stale. vt is a _pointer_ to the data so that
first reference against it is guaranteed to grab the correct value. The
only possible race is between the if and the set_cursor, but that isn't
an issue because we acquired the console semaphore. There is no race
here.
> > Please, for all that is righteous, apply.
>
> please fix it better first...
> (unless I am mistaken).
Thus, unless I am mistaken, it is fine. Please, apply.
Robert Love
next prev parent reply other threads:[~2001-12-11 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 1:51 [PATCH] console close race fix resend Robert Love
2001-12-11 3:16 ` Gordon Oliver
2001-12-11 6:05 ` Robert Love [this message]
2001-12-11 6:28 ` Andrew Morton
2001-12-11 9:05 ` [PATCH] " Robert Love
2001-12-11 8:54 ` [PATCH] " Gordon Oliver
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=1008050718.4287.11.camel@phantasy \
--to=rml@tech9.net \
--cc=gordo@pincoya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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