public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Lee <leeben@linux.vnet.ibm.com>
To: davem@davemloft.net, linux-kernel@vger.kernel.org
Cc: dany@us.ibm.com, dany4madden@gmail.com, benjamin.fik.lee@gmail.com
Subject: Re: [PATCH] Made bpf_internal_load_pointer_neg_helper static: fixes Sparse warning
Date: Mon, 11 Aug 2014 15:00:56 -0700	[thread overview]
Message-ID: <1407794456.12335.3.camel@oc1318858833.ibm.com> (raw)
In-Reply-To: <1405708449.11800.2.camel@oc1318858833.ibm.com>

I wanted to know what the current status of my patch is since my
internship will be ending this Friday and I want to know before then. if
there are any problems with it I can fix them before Thursday. Thank you
in advance.

On Fri, 2014-07-18 at 11:34 -0700, Benjamin Lee wrote:
> This patch fixes the following Sparse warning:
> 
> net/core/filter.c:52:6: warning: symbol
> 'bpf_internal_load_pointer_neg_helper' was not declared. Should it be
> static?
> 
> I declared bpf_internal_load_pointer_neg_helper as static because it  
> is not referenced elsewhere in the kernel. The patched kernel boots  
> and runs OK. I verified that the section of code is actually being  
> compiled by temporarily placing a #pragma message inside the function.  
> I also verified that the function is being called by temporarily  
> inserting a call to panic.
> 
> I am a high school student trying to become familiar with the open  
> source process and the Linux kernel, so your guidance is appreciated.
> 
> Signed-off-by Benjamin Lee <leeben@linux.vnet.ibm.com>
> Reviewed-by: Dany Madden <danymadden@us.ibm.com>
> Reviewed-by: Jim Keniston <jkenisto@us.ibm.com>
> 
> ---
>   net/core/filter.c |    3 ++-
>   1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/net/core/filter.c b/net/core/filter.c
> index 735fad8..068442a 100644
> --- a/net/core/filter.c
> +++ b/net/core/filter.c
> @@ -70,7 +70,8 @@
>    *
>    * Exported for the bpf jit load helper.
>    */
> -void *bpf_internal_load_pointer_neg_helper(const struct sk_buff *skb, int k, unsigned int size)
> +static void *bpf_internal_load_pointer_neg_helper(const struct sk_buff *skb,
> +                                                 int k, unsigned int
> size)
>   {
>         u8 *ptr = NULL;
> 



       reply	other threads:[~2014-08-11 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1405708449.11800.2.camel@oc1318858833.ibm.com>
2014-08-11 22:00 ` Benjamin Lee [this message]
2014-08-12  0:57   ` [PATCH] Made bpf_internal_load_pointer_neg_helper static: fixes Sparse warning Alexei Starovoitov
2014-08-12  5:21     ` Daniel Borkmann

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=1407794456.12335.3.camel@oc1318858833.ibm.com \
    --to=leeben@linux.vnet.ibm.com \
    --cc=benjamin.fik.lee@gmail.com \
    --cc=dany4madden@gmail.com \
    --cc=dany@us.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@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