Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: christoph.paasch@uclouvain.be
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] Fix: sparse warning in inet_csk_prepare_forced_close
Date: Thu, 07 Mar 2013 16:31:54 -0500 (EST)	[thread overview]
Message-ID: <20130307.163154.1852978287105127033.davem@davemloft.net> (raw)
In-Reply-To: <1362659673-28895-1-git-send-email-christoph.paasch@uclouvain.be>

From: Christoph Paasch <christoph.paasch@uclouvain.be>
Date: Thu,  7 Mar 2013 13:34:33 +0100

> In e337e24d66 (inet: Fix kmemleak in tcp_v4/6_syn_recv_sock and
> dccp_v4/6_request_recv_sock) I introduced the function
> inet_csk_prepare_forced_close, which does a call to bh_unlock_sock().
> This produces a sparse-warning.
> 
> This patch adds the missing __releases.
> 
> Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
> ---
>  net/ipv4/inet_connection_sock.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/net/ipv4/inet_connection_sock.c b/net/ipv4/inet_connection_sock.c
> index 7d1874b..804c98f 100644
> --- a/net/ipv4/inet_connection_sock.c
> +++ b/net/ipv4/inet_connection_sock.c
> @@ -735,6 +735,7 @@ EXPORT_SYMBOL(inet_csk_destroy_sock);
>   * tcp/dccp_create_openreq_child().
>   */
>  void inet_csk_prepare_forced_close(struct sock *sk)
> +__releases(&sk->sk_lock.slock)

This should be indented by one TAB, I fixed this while applying your
patch, thanks.

      reply	other threads:[~2013-03-07 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 12:34 [PATCH] Fix: sparse warning in inet_csk_prepare_forced_close Christoph Paasch
2013-03-07 21:31 ` David Miller [this message]

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=20130307.163154.1852978287105127033.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=christoph.paasch@uclouvain.be \
    --cc=netdev@vger.kernel.org \
    /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