All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Paolo Ciarrocchi <ciarrocchi@linuxmail.org>,
	Matt Reppert <arashi@arashi.yi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: poll-related "scheduling while atomic", 2.5.44-mm6
Date: Tue, 29 Oct 2002 22:27:09 -0800	[thread overview]
Message-ID: <3DBF7BBD.795AFC0E@digeo.com> (raw)
In-Reply-To: 20021029223856.21280.qmail@linuxmail.org

Paolo Ciarrocchi wrote:
> 
> >> So my guess is somewhere between -mm5 and -mm6 we
> >> screwed up the atomicity count.
> >Mine too.  I'll check it out, thanks.
> 
> The same here as well
> 

This'll fix it up.  Whoever invented cut-n-paste has a lot to
answer for.


--- 25/mm/swap.c~preempt-count-fix	Tue Oct 29 22:19:54 2002
+++ 25-akpm/mm/swap.c	Tue Oct 29 22:20:16 2002
@@ -90,11 +90,12 @@ void lru_cache_add_active(struct page *p
 
 void lru_add_drain(void)
 {
-	struct pagevec *pvec = &per_cpu(lru_add_pvecs, get_cpu());
+	int cpu = get_cpu();
+	struct pagevec *pvec = &per_cpu(lru_add_pvecs, cpu);
 
 	if (pagevec_count(pvec))
 		__pagevec_lru_add(pvec);
-	pvec = &per_cpu(lru_add_active_pvecs, get_cpu());
+	pvec = &per_cpu(lru_add_active_pvecs, cpu);
 	if (pagevec_count(pvec))
 		__pagevec_lru_add_active(pvec);
 	put_cpu();

.

I had a crash while testing SMP+preempt btw.  Nasty one - took a
pagefault from userspace but do_page_fault() decided that the
fault was in-kernel or something.  It fell all the way through
to die() and, well, died.  I saw the same happen some months ago.

  reply	other threads:[~2002-10-30  6:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 22:38 poll-related "scheduling while atomic", 2.5.44-mm6 Paolo Ciarrocchi
2002-10-30  6:27 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-29 21:37 Matt Reppert
2002-10-29 22:19 ` Andrew Morton
2002-10-29 23:55   ` Matt Reppert

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=3DBF7BBD.795AFC0E@digeo.com \
    --to=akpm@digeo.com \
    --cc=arashi@arashi.yi.org \
    --cc=ciarrocchi@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.