From: Alexei Starovoitov <ast@fb.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Jann Horn <jannh@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
<netdev@vger.kernel.org>, <kernel-team@fb.com>
Subject: [PATCH net 3/3] samples/bpf: fix trace_output example
Date: Wed, 27 Apr 2016 18:56:22 -0700 [thread overview]
Message-ID: <1461808582-1452466-4-git-send-email-ast@fb.com> (raw)
In-Reply-To: <1461808582-1452466-1-git-send-email-ast@fb.com>
llvm cannot always recognize memset as builtin function and optimize
it away, so just delete it. It was a leftover from testing
of bpf_perf_event_output() with large data structures.
Fixes: 39111695b1b8 ("samples: bpf: add bpf_perf_event_output example")
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
---
samples/bpf/trace_output_kern.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/samples/bpf/trace_output_kern.c b/samples/bpf/trace_output_kern.c
index 8d8d1ec429eb..9b96f4fb8cea 100644
--- a/samples/bpf/trace_output_kern.c
+++ b/samples/bpf/trace_output_kern.c
@@ -18,7 +18,6 @@ int bpf_prog1(struct pt_regs *ctx)
u64 cookie;
} data;
- memset(&data, 0, sizeof(data));
data.pid = bpf_get_current_pid_tgid();
data.cookie = 0x12345678;
--
2.8.0
next prev parent reply other threads:[~2016-04-28 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 1:56 [PATCH net 0/3] bpf: fix several bugs Alexei Starovoitov
2016-04-28 1:56 ` [PATCH net 1/3] bpf: fix refcnt overflow Alexei Starovoitov
2016-04-28 1:56 ` [PATCH net 2/3] bpf: fix check_map_func_compatibility logic Alexei Starovoitov
2016-04-28 9:31 ` Jann Horn
2016-04-28 1:56 ` Alexei Starovoitov [this message]
2016-04-28 21:30 ` [PATCH net 0/3] bpf: fix several bugs David Miller
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=1461808582-1452466-4-git-send-email-ast@fb.com \
--to=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jannh@google.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).