From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/2] bpf: sockmap, double free in __sock_map_ctx_update_elem()
Date: Fri, 18 May 2018 19:17:57 -0500 [thread overview]
Message-ID: <b5667bc9-0c43-c8aa-1963-92f3e8884b7a@embeddedor.com> (raw)
In-Reply-To: <20180518143930.hopqsx3sbrbsxlfp@mwanda>
Hi Dan,
On 05/18/2018 09:39 AM, Dan Carpenter wrote:
> On Fri, May 18, 2018 at 10:27:18AM +0200, Daniel Borkmann wrote:
>>
>> Thanks for the two fixes, appreciate it! There were two similar ones that
>> fix the same issues which were already applied yesterday to bpf-next:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=0e4364560361d57e8cd873a8990327f3471d7d8a
>> https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=a78622932c27e8ec33e5ba180f3d2e87fb806b28
>
> Hey Gustavo,
>
> We're sort of duplicating each other's work. Could you CC
> kernel-janitors@vger.kernel.org for static checker fixes so that I can
> see what you're working on?
>
Sure thing.
I've been doing this work for more than a year now and just recently we
are having these issues. I'm a bit curious about it.
> We'll probably still send the occasional duplicate which is fine...
>
Yep. Not a big deal for me.
Have a good one.
prev parent reply other threads:[~2018-05-19 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 7:58 [PATCH 1/2] bpf: sockmap, double free in __sock_map_ctx_update_elem() Dan Carpenter
2018-05-18 8:27 ` Daniel Borkmann
2018-05-18 14:39 ` Dan Carpenter
2018-05-19 0:17 ` Gustavo A. R. Silva [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:
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=b5667bc9-0c43-c8aa-1963-92f3e8884b7a@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=ast@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--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