public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: George Anzinger <george@mvista.com>,
	john stultz <johnstul@us.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: 2.6.15-rt4-sr1
Date: Wed, 11 Jan 2006 15:47:11 -0500	[thread overview]
Message-ID: <1137012431.6197.117.camel@localhost.localdomain> (raw)

I've just uploaded my new maintenance release.

fixes:

- light soft lockup - currently it doesn't detect the light soft lockups
    because the counter was being reset in the wrong place.  Not sure if
    this was done earlier with some other issue.  But I needed this fix
    to get the low priority lockup to be detected.

- posix_timers deadlock - There's a loop in the posix_timeres code that 
    is entered if the current process is a higher priority than the 
    softirqd thread, and it spins until the softirqd thread is finished.
    But since the thread is of a higher priority than the softirqd, it
    deadlocks.

- read_trylock_rt  - added this for cases that have a loop on
    read_trylock.  Since in RT a read lock is a mutex, a read_trylock
    will fail even if the owner has it only for reading.  But since
    the reads are not protected with irqsaves, this can deadlock when
    a high priority process preempts the owner of the lock and spins
    till it's released. (this was seen in signal.c: send_group_sigqueue,
    there may be others)

Still at the normal location:

http://home.stny.rr.com/rostedt/patches/patch-2.6.15-rt4-sr1

Here is the program that showed all these nice deadlocks ;)

http://www.kihontech.com/tests/rt/timer_stress.c

(Run with -P to get the posix deadlocks)

-- Steve



             reply	other threads:[~2006-01-11 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 20:47 Steven Rostedt [this message]
2006-01-11 21:16 ` 2.6.15-rt4-sr1 Thomas Gleixner

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=1137012431.6197.117.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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