All of
 help / color / mirror / Atom feed
From: Jakub Kicinski <>
To: Daniel Borkmann <>
Subject: Re: pull-request: bpf 2020-05-09
Date: Fri, 8 May 2020 19:02:00 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat,  9 May 2020 01:05:27 +0200 Daniel Borkmann wrote:
> Hi David,
> The following pull-request contains BPF updates for your *net* tree.
> We've added 4 non-merge commits during the last 9 day(s) which contain
> a total of 4 files changed, 11 insertions(+), 6 deletions(-).
> The main changes are:
> 1) Fix msg_pop_data() helper incorrectly setting an sge length in some
>    cases as well as fixing bpf_tcp_ingress() wrongly accounting bytes
>    in sg.size, from John Fastabend.
> 2) Fix to return an -EFAULT error when copy_to_user() of the value
>    fails in map_lookup_and_delete_elem(), from Wei Yongjun.
> 3) Fix sk_psock refcnt leak in tcp_bpf_recvmsg(), from Xiyu Yang.

Pulled, thank you!

      reply	other threads:[~2020-05-09  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 23:05 pull-request: bpf 2020-05-09 Daniel Borkmann
2020-05-09  2:02 ` Jakub Kicinski [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.