From: Ivo van Doorn <ivdoorn@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kionez <kionez@anche.no>
Subject: Re: [PATCH 2/2] rfkill: ignore errors from rfkill_toggle_radio in rfkill_add_switch
Date: Thu, 3 Jul 2008 18:25:00 +0200 [thread overview]
Message-ID: <200807031825.00955.IvDoorn@gmail.com> (raw)
In-Reply-To: <1215101697-30576-3-git-send-email-hmh@hmh.eng.br>
On Thursday 03 July 2008, Henrique de Moraes Holschuh wrote:
> rfkill_add_switch() calls rfkill_toggle_radio() to set the state of a
> recently registered rfkill class to the current global state [for that
> rfkill->type].
>
> The rfkill_toggle_radio() call is going to error out if the hardware is
> RFKILL_STATE_HARD_BLOCKED, and the global state is RFKILL_STATE_UNBLOCKED.
>
> That is a quite normal situation which I missed to account for. As things
> stand, the error return from rfkill_toggle_radio ends up causing
> rfkill_register to bail out with an error (de-registering the new switch in
> the process), which is Not Nice.
>
> Change rfkill_add_switch() to not return errors because of a failed call to
> rfkill_toggle_radio(). We can go back to returning errors again (if that's
> indeed the right thing to do) if we define the exact error codes the
> rfkill->toggle_radio callbacks are to return in each situation, so that we
> can ignore the right ones only.
>
> Bug reported by "kionez <kionez@anche.no>".
>
> Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Cc: Ivo van Doorn <IvDoorn@gmail.com>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
> Cc: kionez <kionez@anche.no>
> ---
> net/rfkill/rfkill.c | 10 ++++------
> 1 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/net/rfkill/rfkill.c b/net/rfkill/rfkill.c
> index aa7039d..7a560b7 100644
> --- a/net/rfkill/rfkill.c
> +++ b/net/rfkill/rfkill.c
> @@ -501,17 +501,15 @@ static struct class rfkill_class = {
>
> static int rfkill_add_switch(struct rfkill *rfkill)
> {
> - int error;
> -
> mutex_lock(&rfkill_mutex);
>
> - error = rfkill_toggle_radio(rfkill, rfkill_states[rfkill->type], 0);
> - if (!error)
> - list_add_tail(&rfkill->node, &rfkill_list);
> + rfkill_toggle_radio(rfkill, rfkill_states[rfkill->type], 0);
> +
> + list_add_tail(&rfkill->node, &rfkill_list);
>
> mutex_unlock(&rfkill_mutex);
>
> - return error;
> + return 0;
> }
>
> static void rfkill_remove_switch(struct rfkill *rfkill)
next prev parent reply other threads:[~2008-07-03 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 16:14 [GIT PATCH] rfkill fixes Henrique de Moraes Holschuh
2008-07-03 16:14 ` [PATCH 1/2] rfkill: some minor kernel-doc changes for rfkill_toggle_radio Henrique de Moraes Holschuh
2008-07-03 16:24 ` Ivo van Doorn
2008-07-03 16:14 ` [PATCH 2/2] rfkill: ignore errors from rfkill_toggle_radio in rfkill_add_switch Henrique de Moraes Holschuh
2008-07-03 16:25 ` Ivo van Doorn [this message]
2008-07-03 16:37 ` Tomas Winkler
2008-07-03 16:47 ` Ivo van Doorn
2008-07-03 16:45 ` Tomas Winkler
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=200807031825.00955.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=kionez@anche.no \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).