All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Nathan Lynch <nathanl@austin.ibm.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: [PATCH] fixes for rcu_offline_cpu, rcu_move_batch (2.6.8-rc2)
Date: Mon, 26 Jul 2004 17:01:57 -0700	[thread overview]
Message-ID: <20040726170157.7f4b414c.akpm@osdl.org> (raw)
In-Reply-To: <1090870667.22306.40.camel@pants.austin.ibm.com>

Nathan Lynch <nathanl@austin.ibm.com> wrote:
>
> Hi,
> 
> rcu_offline_cpu and rcu_move_batch have been broken since the
> list_head's in struct rcu_head and struct rcu_data were replaced with
> singly-linked lists:
> 
>   CC      kernel/rcupdate.o
> kernel/rcupdate.c: In function `rcu_move_batch':
> kernel/rcupdate.c:222: warning: passing arg 2 of `list_add_tail' from
> incompatible pointer type
> kernel/rcupdate.c: In function `rcu_offline_cpu':
> kernel/rcupdate.c:239: warning: passing arg 1 of `rcu_move_batch' from
> incompatible pointer type
> kernel/rcupdate.c:240: warning: passing arg 1 of `rcu_move_batch' from
> incompatible pointer type
> kernel/rcupdate.c:236: warning: label `unlock' defined but not used

oop.  We really should find some way to get more people to enable CPU
hotplug.  We have a coverage problem.

> Kernel crashes when you try to offline a cpu, not surprisingly.
> 
> It also looks like rcu_move_batch isn't preempt-safe so I touched that
> up, and got rid of an unused label in rcu_offline_cpu.
> 
> This fixes the crash for me; does it look ok?
> 

Looks good to me, thanks.


  reply	other threads:[~2004-07-27  0:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 19:37 [PATCH] fixes for rcu_offline_cpu, rcu_move_batch (2.6.8-rc2) Nathan Lynch
2004-07-27  0:01 ` Andrew Morton [this message]
2004-07-27  5:49   ` Zwane Mwaikambo
2004-07-31 20:53     ` [PATCH][2.6-mm] i386 Hotplug CPU Zwane Mwaikambo
2004-07-31 21:01       ` Zwane Mwaikambo
2004-08-01  3:19       ` Zwane Mwaikambo
2004-08-11 13:50       ` Pavel Machek
2004-08-12  0:44         ` [lhcs-devel] " Zwane Mwaikambo
2004-08-15  3:19           ` Zwane Mwaikambo
2004-08-15 14:46             ` Pavel Machek
2004-08-15 15:03               ` Zwane Mwaikambo

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=20040726170157.7f4b414c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=rusty@rustcorp.com.au \
    /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.