From: Ingo Molnar <mingo@elte.hu>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
H Peter Anvin <hpa@zytor.com>, Len Brown <lenb@kernel.org>,
Jin Dongming <jin.dongming@np.css.fujitsu.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Jean Delvare <khali@linux-fr.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH] therm_throt.c: Fix error handling in thermal_throttle_add_dev
Date: Fri, 3 Sep 2010 11:35:53 +0200 [thread overview]
Message-ID: <20100903093553.GA6821@elte.hu> (raw)
In-Reply-To: <1283474726-20109-1-git-send-email-fenghua.yu@intel.com>
* Fenghua Yu <fenghua.yu@intel.com> wrote:
> From: Fenghua Yu <fenghua.yu@intel.com>
>
> Warn when sysfs_add_file_to_group fails.
>
> Also add missing curly braces.
>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> ---
> arch/x86/kernel/cpu/mcheck/therm_throt.c | 14 ++++++++++----
> 1 files changed, 10 insertions(+), 4 deletions(-)
> + WARN_ON(err);
Hm, we tend to use WARN_ON_ONCE(), to avoid repeat spamming of the
syslog. Also, and perhaps more importantly, WARN_ON() is not a
particularly smart way to handle errors. How do other drivers handle
sysfs registration failures?
Also, that's not the only thing the patch does:
> @@ -211,20 +211,26 @@ static __cpuinit int thermal_throttle_add_dev(struct sys_device *sys_dev)
> - return err;
> + return 0;
How is the ignoring of an error and turning it into a WARN_ON() a fix?
Either it makes no sense to return errors - in which case the whole
add_dev method needs to be fixed in all drivers - or it makes sense, in
which case the behavior here is inconsistent.
At minimum more explanation is needed in the changelog.
Thanks,
Ingo
next prev parent reply other threads:[~2010-09-03 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 0:45 [PATCH] therm_throt.c: Fix error handling in thermal_throttle_add_dev Fenghua Yu
2010-09-03 8:48 ` Jean Delvare
2010-09-03 9:35 ` Ingo Molnar [this message]
2010-09-03 21:34 ` Fenghua Yu
2010-09-05 12:32 ` Ingo Molnar
2010-09-05 16:35 ` [lm-sensors] " Guenter Roeck
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=20100903093553.GA6821@elte.hu \
--to=mingo@elte.hu \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
/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