From: Daniel Walker <dwalker@mvista.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu
Subject: RT and Signals
Date: 11 Apr 2005 10:14:27 -0700 [thread overview]
Message-ID: <1113239666.30549.37.camel@dhcp153.mvista.com> (raw)
I'm not sure if this has changed at all in recent RT patches, but I've
noticed several issues popping up that are related to the timer
interrupt sending signals , one in particular is the fact that
send_sig() calls into __cache_alloc() which has it's interrupt disable
protections removed in RT . I've observed slab corruption due to this
while running lmbench and LTP .
Another issue was a livelock related to the timer interrupt calling
send_sig which locks tasklist_lock and siglock , which are both mutexes
(deadlock detect was on , but didn't trigger)..
LTP and lmbench seem to bring all these issues to the surface, but they
are all different depending on the architecture. I've been treating the
symptoms , but not the disease .. Ultimately , we need some protections,
in signal deliver, to stop the timer interrupt ..
Daniel
next reply other threads:[~2005-04-11 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 17:14 Daniel Walker [this message]
2005-04-11 18:03 ` john cooper
2005-04-11 18:37 ` Daniel Walker
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=1113239666.30549.37.camel@dhcp153.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®