From: Hillf Danton <hdanton@sina.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] bpf_prog_free_deferred bug. WAS: Re: WARNING in mark_chain_precision
Date: Fri, 12 Jul 2019 00:00:25 +0800 [thread overview]
Message-ID: <20190711160025.8796-1-hdanton@sina.com> (raw)
On Thu, 11 Jul 2019 07:29:42 +0800 Andrii Nakryiko wrote:
>
> I'm curious what makes BPF_PROG_TYPE_SOCKET_FILTER (and
Me too. And thanks to folks casting light on it.
> BPF_PROG_TYPE_SK_REUSEPORT) special, compared to all the other types
> of BPF programs. If it's something to do with sockets specifically,
> there are a bunch of other programs that deal with sockets, so should
> they be handled specially as well (e.g., BPF_PROG_TYPE_CGROUP_SOCK)?
>
> Daniel, do you have any insight here?
next reply other threads:[~2019-07-11 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 16:00 Hillf Danton [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-09 3:49 [Intel-wired-lan] WARNING in mark_chain_precision Andrii Nakryiko
2019-07-09 4:25 ` syzbot
2019-07-10 23:29 ` [Intel-wired-lan] bpf_prog_free_deferred bug. WAS: " Andrii Nakryiko
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=20190711160025.8796-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=intel-wired-lan@osuosl.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