From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: akpm@osdl.org
Cc: neilb@suse.de, michal.k.k.piotrowski@gmail.com,
rusty@rustcorp.com.au, "LKML" <linux-kernel@vger.kernel.org>
Subject: Re: + convert-cpu-hotplug-notifiers-to-use-raw_notifier-instead-of-blocking_notifier.patch added to -mm tree
Date: Fri, 13 Oct 2006 17:19:16 +0200 [thread overview]
Message-ID: <452FAE74.1020500@googlemail.com> (raw)
In-Reply-To: <200610130506.k9D56YJY031111@shell0.pdx.osdl.net>
Hi,
akpm@osdl.org wrote:
> The patch titled
>
> Convert cpu hotplug notifiers to use raw_notifier instead of blocking_notifier
>
> has been added to the -mm tree. Its filename is
>
> convert-cpu-hotplug-notifiers-to-use-raw_notifier-instead-of-blocking_notifier.patch
>
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
>
> ------------------------------------------------------
> Subject: Convert cpu hotplug notifiers to use raw_notifier instead of blocking_notifier
> From: Neil Brown <neilb@suse.de>
>
> The use of blocking notifier by _cpu_up and _cpu_down in cpu.c has two
> problem.
>
> 1/ An interaction with the workqueue notifier causes lockdep to spit a
> warning.
>
> 2/ A notifier could conceivable be added or removed while _cpu_up or
> _cpu_down are in process. As each notifier is called twice (prepare
> then commit/abort) this could be unhealthy.
>
> To fix to we simply take cpu_add_remove_lock while adding or removing
> notifiers to/from the list.
>
> This makes the 'blocking' usage unnecessary as all accesses to cpu_chain
> are now protected by cpu_add_remove_lock. So change "blocking" to "raw" in
> all relevant places. This fixes 1.
>
There is something really wrong with this patch (or my hardware).
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
works fine for me on 2.6.19-rc1-g8770c018.
On 2.6.19-rc1-mm1 +
convert-cpu-hotplug-notifiers-to-use-raw_notifier-instead-of-blocking_notifier.patch
+ Neil's avoid_lockdep_warning_in_md.patch
(http://www.ussg.iu.edu/hypermail/linux/kernel/0610.1/0642.html)
I get a lot of "end_request: I/O error, dev sda, sector 31834343" messages.
I checked sda with badblocks and everything seems to be fine
/sbin/badblocks -o /root/sda.badblocks -v /dev/sda
Sprawdzanie bloków od 0 do 156290904
Poszukiwanie wadliwych bloków (tylko odczyt): done
Przebieg zakończony, znaleziono 0 wadliwych bloków.
(/root/sda.badblocks is empty)
BTW. sda is a new Seagate SATA II HDD atached to ICH5 (SATA I) controller.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
next parent reply other threads:[~2006-10-13 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610130506.k9D56YJY031111@shell0.pdx.osdl.net>
2006-10-13 15:19 ` Michal Piotrowski [this message]
2006-10-13 18:41 ` + convert-cpu-hotplug-notifiers-to-use-raw_notifier-instead-of-blocking_notifier.patch added to -mm tree Andrew Morton
2006-10-13 20:13 ` Michal Piotrowski
2006-10-13 20:43 ` Andrew Morton
2006-10-14 6:55 ` Andrew Morton
2006-10-14 11:53 ` Michal Piotrowski
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=452FAE74.1020500@googlemail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--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.