From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Shawn Starr <spstarr@sh0n.net>
Cc: Andrew Morton <akpm@digeo.com>,
rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: [OOPS][2.5.66bk3+] run_timer_softirq - IRQ Mishandlings - New OOPS w/ timer
Date: Sun, 30 Mar 2003 19:12:57 +0200 [thread overview]
Message-ID: <20030330171257.GC26557@vana.vc.cvut.cz> (raw)
In-Reply-To: <000b01c2f6d6$f843eab0$030aa8c0@unknown>
On Sun, Mar 30, 2003 at 11:10:48AM -0500, Shawn Starr wrote:
> Function found was: delayed_work_timer_fn (kernel/workqueue.c)
>
> free of pending timer at c7411150
> function=c0138ba0
> Call Trace:
> [<c014d4b4>] timer_hunt+0x84/0x90
> [<c0138ba0>] delayed_work_timer_fn+0x0/0x170
> [<c014fb08>] kfree+0x1c8/0x320
> [<c024f8a6>] release_dev+0x696/0x840
> [<c024f8a6>] release_dev+0x696/0x840
drivers/char/tty_io.c schedules flush_to_ldisc work. This
work can potentially reschedule itself, making call to
flush_scheduled_work() at the end of release_dev()
useless :-(
Unfortunately I have no idea what is that code trying to do -
we already did tty->ldisc.close() and replaced
tty->ldisc with something else when we call flush_scheduled_work(),
so I doubt that work we are waiting for can do anything
useful even if TTY_DONT_FLIP is not set...
Petr Vandrovec
vandrove@vc.cvut.cz
next prev parent reply other threads:[~2003-03-30 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 16:10 Shawn Starr
2003-03-30 17:12 ` Petr Vandrovec [this message]
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 ` [OOPS][2.5.66bk9+] " Shawn Starr
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=20030330171257.GC26557@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=spstarr@sh0n.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
all inboxes | Powered by JetHome®