linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-wireless@vger.kernel.org, Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH 3/8] rfkill: add __must_check annotations
Date: Sun, 3 Aug 2008 10:05:37 +0200	[thread overview]
Message-ID: <200808031005.37299.IvDoorn@gmail.com> (raw)
In-Reply-To: <1217700664-20792-4-git-send-email-hmh@hmh.eng.br>

On Saturday 02 August 2008, Henrique de Moraes Holschuh wrote:
> rfkill is not a small, mere detail in wireless support.  Once it starts
> supporting rfkill and users start counting on that support, a wireless
> device is at risk of operating in dangerous conditions should rfkill
> support fail to properly activate.
> 
> Therefore, add the required __must_check annotations on some key functions
> of the rfkill API, for which the wireless drivers absolutely MUST handle
> the failure mode safely in order to avoid a potentially dangerous situation
> where the wireless transmitter is left enabled when the user don't want it
> to.
> 
> Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Cc: Ivo van Doorn <IvDoorn@gmail.com>
> Cc: Matthew Garrett <mjg@redhat.com>

Acked-by: Ivo van Doorn <IvDoorn@gmail.com>

> ---
>  include/linux/rfkill.h |    5 +++--
>  net/rfkill/rfkill.c    |    5 +++--
>  2 files changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/include/linux/rfkill.h b/include/linux/rfkill.h
> index aa3c7d5..e92d8e9 100644
> --- a/include/linux/rfkill.h
> +++ b/include/linux/rfkill.h
> @@ -110,9 +110,10 @@ struct rfkill {
>  };
>  #define to_rfkill(d)	container_of(d, struct rfkill, dev)
>  
> -struct rfkill *rfkill_allocate(struct device *parent, enum rfkill_type type);
> +struct rfkill * __must_check rfkill_allocate(struct device *parent,
> +					     enum rfkill_type type);
>  void rfkill_free(struct rfkill *rfkill);
> -int rfkill_register(struct rfkill *rfkill);
> +int __must_check rfkill_register(struct rfkill *rfkill);
>  void rfkill_unregister(struct rfkill *rfkill);
>  
>  int rfkill_force_state(struct rfkill *rfkill, enum rfkill_state state);
> diff --git a/net/rfkill/rfkill.c b/net/rfkill/rfkill.c
> index c1901fb..5320210 100644
> --- a/net/rfkill/rfkill.c
> +++ b/net/rfkill/rfkill.c
> @@ -653,7 +653,8 @@ static void rfkill_remove_switch(struct rfkill *rfkill)
>   * NOTE: If registration fails the structure shoudl be freed by calling
>   * rfkill_free() otherwise rfkill_unregister() should be used.
>   */
> -struct rfkill *rfkill_allocate(struct device *parent, enum rfkill_type type)
> +struct rfkill * __must_check rfkill_allocate(struct device *parent,
> +					     enum rfkill_type type)
>  {
>  	struct rfkill *rfkill;
>  	struct device *dev;
> @@ -724,7 +725,7 @@ static void rfkill_led_trigger_unregister(struct rfkill *rfkill)
>   * structure needs to be registered. Immediately from registration the
>   * switch driver should be able to service calls to toggle_radio.
>   */
> -int rfkill_register(struct rfkill *rfkill)
> +int __must_check rfkill_register(struct rfkill *rfkill)
>  {
>  	static atomic_t rfkill_no = ATOMIC_INIT(0);
>  	struct device *dev = &rfkill->dev;



  reply	other threads:[~2008-08-03  7:42 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 18:10 [GIT PATCH] rfkill changes for 2.6.28, set 1 Henrique de Moraes Holschuh
2008-08-02 18:10 ` [PATCH 1/8] rfkill: detect bogus double-registering (v2) Henrique de Moraes Holschuh
2008-08-03  8:04   ` Ivo van Doorn
2008-08-02 18:10 ` [PATCH 2/8] rfkill: add default global states (v2) Henrique de Moraes Holschuh
2008-08-03  8:05   ` Ivo van Doorn
2008-08-02 18:10 ` [PATCH 3/8] rfkill: add __must_check annotations Henrique de Moraes Holschuh
2008-08-03  8:05   ` Ivo van Doorn [this message]
2008-08-02 18:11 ` [PATCH 4/8] rfkill: introduce RFKILL_STATE_MAX Henrique de Moraes Holschuh
2008-08-03  8:06   ` Ivo van Doorn
2008-08-02 18:11 ` [PATCH 5/8] rfkill: add WARN_ON and BUG_ON paranoia Henrique de Moraes Holschuh
2008-08-03  8:07   ` Ivo van Doorn
2008-08-03  8:57     ` Johannes Berg
2008-08-03 10:07       ` Ivo van Doorn
2008-08-03 13:28         ` Henrique de Moraes Holschuh
2008-08-03 13:53           ` Ivo van Doorn
2008-08-03 13:36             ` Henrique de Moraes Holschuh
2008-08-03 13:21       ` Henrique de Moraes Holschuh
2008-08-03 13:50         ` Ivo van Doorn
2008-08-03 18:12         ` Johannes Berg
2008-08-02 18:11 ` [PATCH 6/8] rfkill: use the new WARN() Henrique de Moraes Holschuh
2008-08-03  8:10   ` Ivo van Doorn
2008-08-03 13:32     ` Henrique de Moraes Holschuh
2008-08-02 18:11 ` [PATCH 7/8] rfkill: rename rfkill_mutex to rfkill_global_mutex Henrique de Moraes Holschuh
2008-08-02 18:11 ` [PATCH 8/8] rfkill: add support for wake-on-wireless-packet Henrique de Moraes Holschuh
2008-08-02 19:02   ` Johannes Berg
2008-08-02 19:27     ` Henrique de Moraes Holschuh
2008-08-02 21:21       ` Tomas Winkler
2008-08-03  3:55         ` Henrique de Moraes Holschuh
2008-08-03  6:03           ` Tomas Winkler
2008-08-03 13:52             ` Henrique de Moraes Holschuh
2008-08-03 15:49               ` Tomas Winkler
2008-08-03 18:25                 ` Henrique de Moraes Holschuh
2008-08-03 22:36                   ` Tomas Winkler
2008-08-04  2:52                     ` Henrique de Moraes Holschuh
2008-08-03  8:12       ` Ivo van Doorn
2008-08-03  8:07         ` Tomas Winkler
2008-08-03 13:44           ` Henrique de Moraes Holschuh
2008-08-03 14:12             ` Tomas Winkler
2008-08-04 15:42       ` Dan Williams
2008-08-04 22:30         ` Henrique de Moraes Holschuh
2008-08-04 22:56           ` Dan Williams
2008-08-04 23:35             ` Henrique de Moraes Holschuh
2008-08-05  9:12               ` Johannes Berg
2008-08-05 12:48                 ` Henrique de Moraes Holschuh
2008-08-05 12:50                   ` Johannes Berg
2008-08-05 12:59                     ` Johannes Berg
2008-08-05 20:44                       ` Henrique de Moraes Holschuh
2008-08-05 20:54                         ` Johannes Berg
2008-08-05 13:03               ` Dan Williams
2008-08-05 14:00                 ` John W. Linville
2008-08-05 18:37                   ` Ivo van Doorn

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=200808031005.37299.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mjg@redhat.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).