From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Jeff Garzik <jeff@garzik.org>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Ashok Raj <ashok.raj@intel.com>,
Nathan Lynch <nathanl@austin.ibm.com>
Subject: Re: [PATCH] drivers/base: error handling fixes
Date: Thu, 5 Oct 2006 15:20:06 +0200 [thread overview]
Message-ID: <20061005132006.GD6920@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20061005151546.31b73ab5@gondolin.boeblingen.de.ibm.com>
> > + for_each_online_cpu(cpu) {
> > + sys_dev = get_cpu_sysdev(cpu);
> > + rc = topology_add_dev(sys_dev);
> > + if (rc)
> > + return rc;
> > }
> >
> > register_hotcpu_notifier(&topology_cpu_notifier);
>
> Shouldn't the added attribute groups be removed again in the failure
> case?
>
> Also, it might be a bit overkill to fail the whole initialization
> because of one "bad" cpu. (And the "bad" cpu wouldn't matter if we
> could safely remove non-existent groups :)
This is initcall stuff. The only sane reason why this would fail, would
be an out of memory situation . If we are that early short on memory, we
are in serious trouble anyway. So I doubt it's worth the extra code.
next prev parent reply other threads:[~2006-10-05 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 13:05 [PATCH] drivers/base: error handling fixes Jeff Garzik
2006-10-04 14:44 ` Cornelia Huck
2006-10-04 15:24 ` Cornelia Huck
2006-10-05 8:17 ` Heiko Carstens
2006-10-05 11:16 ` Jeff Garzik
2006-10-05 12:48 ` Heiko Carstens
2006-10-05 12:58 ` Jeff Garzik
2006-10-05 13:16 ` Heiko Carstens
2006-10-09 7:29 ` [patch 1/2] sysfs: allow removal of nonexistent sysfs groups Heiko Carstens
2006-10-09 7:40 ` Andrew Morton
2006-10-09 7:49 ` Heiko Carstens
2006-10-09 7:30 ` [patch 2/2] cpu topology: various fixes/cleanups Heiko Carstens
2006-10-05 13:15 ` [PATCH] drivers/base: error handling fixes Cornelia Huck
2006-10-05 13:20 ` Heiko Carstens [this message]
2006-10-05 13:45 ` Cornelia Huck
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=20061005132006.GD6920@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.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