From: Andrew Morton <akpm@zip.com.au>
To: Robert Love <rml@tech9.net>
Cc: gordo@pincoya.com, marcelo@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] console close race fix resend
Date: Mon, 10 Dec 2001 22:28:42 -0800 [thread overview]
Message-ID: <3C15A79A.98EC0ADB@zip.com.au> (raw)
In-Reply-To: <20011210191630.A13679@furble>, <1008035512.4287.1.camel@phantasy> <20011210191630.A13679@furble> <1008050718.4287.11.camel@phantasy>
Robert Love wrote:
>
> 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();
> }
>
It could be improved - we really should test tty->driver_data inside
lock_kernel(), and after the possible sleep.
How does this look (and how does it test?)
--- linux-2.4.17-pre8/drivers/char/console.c Mon Dec 10 13:46:20 2001
+++ linux-akpm/drivers/char/console.c Mon Dec 10 22:27:05 2001
@@ -100,6 +100,7 @@
#include <linux/tqueue.h>
#include <linux/bootmem.h>
#include <linux/pm.h>
+#include <linux/smp_lock.h>
#include <asm/io.h>
#include <asm/system.h>
@@ -2350,15 +2351,18 @@ static void con_start(struct tty_struct
static void con_flush_chars(struct tty_struct *tty)
{
- struct vt_struct *vt = (struct vt_struct *)tty->driver_data;
+ struct vt_struct *vt;
if (in_interrupt()) /* from flush_to_ldisc */
return;
-
pm_access(pm_con);
+ lock_kernel(); /* versus con_close() */
acquire_console_sem();
- set_cursor(vt->vc_num);
+ vt = (struct vt_struct *)tty->driver_data;
+ if (vt)
+ set_cursor(vt->vc_num);
release_console_sem();
+ unlock_kernel();
}
/*
next prev parent reply other threads:[~2001-12-11 6:30 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
2001-12-11 6:28 ` Andrew Morton [this message]
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=3C15A79A.98EC0ADB@zip.com.au \
--to=akpm@zip.com.au \
--cc=gordo@pincoya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rml@tech9.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