From: "Shawn Starr" <spstarr@sh0n.net>
To: "'Andrew Morton'" <akpm@digeo.com>
Cc: <roland@topspin.com>, <rml@tech9.net>, <linux-kernel@vger.kernel.org>
Subject: RE: [OOPS][2.5.66bk9+] run_timer_softirq - IRQ Mishandlings - New OOPS w/ timer
Date: Sat, 5 Apr 2003 19:35:24 -0500 [thread overview]
Message-ID: <000001c2fbd4$6ae9f030$030aa8c0@unknown> (raw)
In-Reply-To: <20030330151746.4394dd2e.akpm@digeo.com>
Andrew, since the new timer changes made, Things are looking solid so far.
We might want to begin adding things into BK-current no?
Sshd hasn't hung, ttys haven't hung either.
Shawn.
-----Original Message-----
From: Andrew Morton [mailto:akpm@digeo.com]
Sent: Sunday, March 30, 2003 6:18 PM
To: Shawn Starr
Cc: roland@topspin.com; rml@tech9.net; linux-kernel@vger.kernel.org
Subject: Re: [OOPS][2.5.66bk3+] run_timer_softirq - IRQ Mishandlings - New
OOPS w/ timer
"Shawn Starr" <spstarr@sh0n.net> wrote:
>
> drivers/char/tty_io.c - Only
>
> I bet it's this function, there's only a kfree, not destruction of any
> timers.
>
This is fairly foul.
--- 25/drivers/char/tty_io.c~a 2003-03-30 15:12:37.000000000 -0800
+++ 25-akpm/drivers/char/tty_io.c 2003-03-30 15:16:59.000000000 -0800
@@ -1288,6 +1288,8 @@ static void release_dev(struct file * fi
/*
* Make sure that the tty's task queue isn't activated.
*/
+ clear_bit(TTY_DONT_FLIP, &tty->flags);
+ del_timer_sync(&tty->flip.work.timer);
flush_scheduled_work();
/*
_
prev parent reply other threads:[~2003-04-06 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 16:10 [OOPS][2.5.66bk3+] run_timer_softirq - IRQ Mishandlings - New OOPS w/ timer Shawn Starr
2003-03-30 17:12 ` Petr Vandrovec
2003-03-30 21:02 ` Roland Dreier
2003-03-30 21:28 ` Shawn Starr
2003-03-30 23:17 ` Andrew Morton
2003-03-31 0:00 ` Roland Dreier
2003-03-31 14:08 ` Shawn Starr
2003-04-06 0:35 ` Shawn Starr [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='000001c2fbd4$6ae9f030$030aa8c0@unknown' \
--to=spstarr@sh0n.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=roland@topspin.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