Netdev List
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org
Subject: pull-request: bpf 2018-10-14
Date: Sun, 14 Oct 2018 11:09:45 +0200	[thread overview]
Message-ID: <20181014090945.17940-1-daniel@iogearbox.net> (raw)

Hi David,

The following pull-request contains BPF updates for your *net* tree.

The main changes are:

1) Fix xsk map update and delete operation to not call synchronize_net()
   but to piggy back on SOCK_RCU_FREE for sockets instead as we are not
   allowed to sleep under RCU, from Björn.

2) Do not change RLIMIT_MEMLOCK in reuseport_bpf selftest if the process
   already has unlimited RLIMIT_MEMLOCK, from Eric.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Thanks a lot!

----------------------------------------------------------------

The following changes since commit e2a322a0c8ce3d825e8a56c063ce3f81b719083c:

  Merge branch 'net-smc-userspace-breakage-fixes' (2018-10-07 21:06:28 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 

for you to fetch changes up to cee271678d0e3177a25d0fcb2fa5e051d48e4262:

  xsk: do not call synchronize_net() under RCU read lock (2018-10-11 10:19:01 +0200)

----------------------------------------------------------------
Björn Töpel (1):
      xsk: do not call synchronize_net() under RCU read lock

Eric Dumazet (1):
      bpf: do not blindly change rlimit in reuseport net selftest

 kernel/bpf/xskmap.c                         | 10 ++--------
 net/xdp/xsk.c                               |  2 ++
 tools/testing/selftests/net/reuseport_bpf.c | 13 +++++++++----
 3 files changed, 13 insertions(+), 12 deletions(-)

                 reply	other threads:[~2018-10-14 16:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20181014090945.17940-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.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