public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: niklas <niklas@bumby.net>
Cc: linux-kernel@vger.kernel.org, sandeen@sgi.com
Subject: Re: 2.4.18-xfs and the preemptive patch
Date: 01 Apr 2002 16:45:48 -0500	[thread overview]
Message-ID: <1017697549.2940.462.camel@phantasy> (raw)
In-Reply-To: <20020401014743.42630286.niklas@bumby.net>

On Sun, 2002-03-31 at 18:47, niklas wrote:
> I just installed the preemptive ( http://www.tech9.net/rml/linux/ ----
> preempt-kernel-rml-2.4.18-4 )  patch on my 2.4.18-xfs tree and when i
> run this kernel, every process ends with "exited with preempt_count 1
> " ( for example "rc.2[35] exited with preempt_count 1" )
> The number varies from 1 to 41 so far.
> Is this a known issue that there is a fix to, or is it just a
> misconfigurd syslog?

That message is caused by tasks exiting with a nonzero preempt_count. 
The preempt_count is basically a count of the number of spinlocks held,
so it should always be zero when a task exits.  Since it is positive,
you don't have anything to worry about wrt "stability" but the system
may not be preempting at all, which would make the preempt-kernel patch
worthless.

I talked to Steve Lord and Eric Sandeen at SGI and they believe they
know the cause of the problem.  Basically, XFS destroys some data
structures and doesn't unlock the associated lock, but just forgets
about it.  This is not good for kernel preemption.

They think the newest XFS in CVS does not do this anymore, but it still
may in some places.  Can you give it a try and let me know if you still
see the messages?  Especially with the same regularity and value.

	http://oss.sgi.com/projects/xfs/cvs_download.html

Thanks,

	Robert Love


      reply	other threads:[~2002-04-01 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-31 23:47 2.4.18-xfs and the preemptive patch niklas
2002-04-01 21:45 ` Robert Love [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=1017697549.2940.462.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niklas@bumby.net \
    --cc=sandeen@sgi.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