From: John Fastabend <john.fastabend@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: [bpf PATCH v3 0/3] BPF, a couple sockmap fixes
Date: Mon, 23 Apr 2018 15:39:17 -0700 [thread overview]
Message-ID: <20180423223712.16388.63625.stgit@john-Precision-Tower-5810> (raw)
While testing sockmap with more programs (besides our test programs)
I found a couple issues.
The attached series fixes an issue where pinned maps were not
working correctly, blocking sockets returned zero, and an error
path that when the sock hit an out of memory case resulted in a
double page_put() while doing ingress redirects.
See individual patches for more details.
v2: Incorporated Daniel's feedback to use map ops for uref put op
which also fixed the build error discovered in v1.
v3: rename map_put_uref to map_release_uref
---
John Fastabend (3):
bpf: sockmap, map_release does not hold refcnt for pinned maps
bpf: sockmap, sk_wait_event needed to handle blocking cases
bpf: sockmap, fix double page_put on ENOMEM error in redirect path
0 files changed
next reply other threads:[~2018-04-23 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 22:39 John Fastabend [this message]
2018-04-23 22:39 ` [bpf PATCH v3 1/3] bpf: sockmap, map_release does not hold refcnt for pinned maps John Fastabend
2018-04-23 22:39 ` [bpf PATCH v3 2/3] bpf: sockmap, sk_wait_event needed to handle blocking cases John Fastabend
2018-04-23 22:39 ` [bpf PATCH v3 3/3] bpf: sockmap, fix double page_put on ENOMEM error in redirect path John Fastabend
2018-04-23 22:52 ` [bpf PATCH v3 0/3] BPF, a couple sockmap fixes 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=20180423223712.16388.63625.stgit@john-Precision-Tower-5810 \
--to=john.fastabend@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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