From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Christian Brauner <brauner@kernel.org>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>, <netdev@vger.kernel.org>,
<linux-bluetooth@vger.kernel.org>
Subject: [PATCH v1 net-next 0/2] af_unix: Followup fixes for SO_PASSPIDFD.
Date: Tue, 27 Jun 2023 10:43:12 -0700 [thread overview]
Message-ID: <20230627174314.67688-1-kuniyu@amazon.com> (raw)
This series fixes 2 issues introduced by commit 5e2ff6704a27 ("scm: add
SO_PASSPIDFD and SCM_PIDFD").
The 1st patch fixes a warning in scm_pidfd_recv() reported by syzkaller.
The 2nd patch fixes a regression that bluetooth can't be built as module.
Alexander Mikhalitsyn (1):
net: scm: introduce and use scm_recv_unix helper
Kuniyuki Iwashima (1):
af_unix: Skip SCM_PIDFD if scm->pid is NULL.
include/net/scm.h | 39 ++++++++++++++++++++++++++++-----------
net/unix/af_unix.c | 4 ++--
2 files changed, 30 insertions(+), 13 deletions(-)
--
2.30.2
next reply other threads:[~2023-06-27 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 17:43 Kuniyuki Iwashima [this message]
2023-06-27 17:43 ` [PATCH v1 net-next 1/2] af_unix: Skip SCM_PIDFD if scm->pid is NULL Kuniyuki Iwashima
2023-06-27 18:37 ` af_unix: Followup fixes for SO_PASSPIDFD bluez.test.bot
2023-06-27 17:43 ` [PATCH v1 net-next 2/2] net: scm: introduce and use scm_recv_unix helper Kuniyuki Iwashima
2023-06-27 18:10 ` [PATCH v1 net-next 0/2] af_unix: Followup fixes for SO_PASSPIDFD patchwork-bot+netdevbpf
2023-06-27 19:01 ` patchwork-bot+bluetooth
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=20230627174314.67688-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=alexander@mihalicyn.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.