From: patchwork-bot+netdevbpf@kernel.org
To: Abhishek Chauhan <quic_abchauha@quicinc.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ahalaney@redhat.com,
willemdebruijn.kernel@gmail.com, martin.lau@kernel.org,
martin.lau@linux.dev, daniel@iogearbox.net, bpf@vger.kernel.org,
kernel@quicinc.com,
syzbot+d7b227731ec589e7f4f0@syzkaller.appspotmail.com,
syzbot+30a35a2e9c5067cc43fa@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next v2] net: validate SO_TXTIME clockid coming from userspace
Date: Sat, 01 Jun 2024 22:50:28 +0000 [thread overview]
Message-ID: <171728222897.32002.3866556698576505524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240529183130.1717083-1-quic_abchauha@quicinc.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 May 2024 11:31:30 -0700 you wrote:
> Currently there are no strict checks while setting SO_TXTIME
> from userspace. With the recent development in skb->tstamp_type
> clockid with unsupported clocks results in warn_on_once, which causes
> unnecessary aborts in some systems which enables panic on warns.
>
> Add validation in setsockopt to support only CLOCK_REALTIME,
> CLOCK_MONOTONIC and CLOCK_TAI to be set from userspace.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: validate SO_TXTIME clockid coming from userspace
https://git.kernel.org/netdev/net-next/c/73451e9aaa24
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-01 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 18:31 [PATCH net-next v2] net: validate SO_TXTIME clockid coming from userspace Abhishek Chauhan
2024-05-30 0:24 ` Willem de Bruijn
2024-06-01 22:50 ` patchwork-bot+netdevbpf [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=171728222897.32002.3866556698576505524.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahalaney@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@quicinc.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_abchauha@quicinc.com \
--cc=syzbot+30a35a2e9c5067cc43fa@syzkaller.appspotmail.com \
--cc=syzbot+d7b227731ec589e7f4f0@syzkaller.appspotmail.com \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox