From: Martin KaFai Lau <martin.lau@linux.dev>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Kuniyuki Iwashima <kuni1840@gmail.com>,
bpf@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH v1 bpf-next 0/2] bpf: Misc changes around AF_UNIX.
Date: Wed, 4 Feb 2026 14:44:18 -0800 [thread overview]
Message-ID: <f08dc67a-059f-4f5c-86c1-4c51b8939b56@linux.dev> (raw)
In-Reply-To: <20260203213442.682838-1-kuniyu@google.com>
On 2/3/26 1:30 PM, Kuniyuki Iwashima wrote:
> Patch 1 adapts sk_is_XXX() helpers in __cgroup_bpf_run_filter_sock_addr().
> Patch 2 removes an unnecessary sk_fullsock() in bpf_skc_to_unix_sock().
>
>
> Kuniyuki Iwashima (2):
> bpf: Use sk_is_inet() and sk_is_unix() in
> __cgroup_bpf_run_filter_sock_addr().
> bpf: Don't check sk_fullsock() in bpf_skc_to_unix_sock().
>
> kernel/bpf/cgroup.c | 6 +-----
> net/core/filter.c | 2 +-
The bot is slow. The change in filter.c is small and the cycle is
closing, so I have landed them to the bpf_next/master.
I just noticed the netdev list is not in cc, so added it here also.
prev parent reply other threads:[~2026-02-04 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 21:30 [PATCH v1 bpf-next 0/2] bpf: Misc changes around AF_UNIX Kuniyuki Iwashima
2026-02-03 21:30 ` [PATCH v1 bpf-next 1/2] bpf: Use sk_is_inet() and sk_is_unix() in __cgroup_bpf_run_filter_sock_addr() Kuniyuki Iwashima
2026-02-03 21:30 ` [PATCH v1 bpf-next 2/2] bpf: Don't check sk_fullsock() in bpf_skc_to_unix_sock() Kuniyuki Iwashima
2026-02-04 1:52 ` [PATCH v1 bpf-next 0/2] bpf: Misc changes around AF_UNIX Stanislav Fomichev
2026-02-04 22:44 ` Martin KaFai Lau [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=f08dc67a-059f-4f5c-86c1-4c51b8939b56@linux.dev \
--to=martin.lau@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--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 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.