From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Abhishek Chauhan <quic_abchauha@quicinc.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Halaney <ahalaney@redhat.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Martin KaFai Lau <martin.lau@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf <bpf@vger.kernel.org>
Cc: kernel@quicinc.com,
syzbot+d7b227731ec589e7f4f0@syzkaller.appspotmail.com,
syzbot+30a35a2e9c5067cc43fa@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: validate SO_TXTIME clockid coming from userspace
Date: Wed, 29 May 2024 09:58:32 -0400 [thread overview]
Message-ID: <665734886e2a9_31b2672946e@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20240528224935.1020828-1-quic_abchauha@quicinc.com>
minor: double space before userspace
Abhishek Chauhan 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.
>
> Link: https://lore.kernel.org/netdev/bc037db4-58bb-4861-ac31-a361a93841d3@linux.dev/
> Link: https://lore.kernel.org/lkml/20240509211834.3235191-1-quic_abchauha@quicinc.com/
These discussions can be found directly from the referenced commit?
If any, I'd like to the conversation we had that arrived at this
approach.
> Fixes: 1693c5db6ab8 ("net: Add additional bit to support clockid_t timestamp type")
> Reported-by: syzbot+d7b227731ec589e7f4f0@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=d7b227731ec589e7f4f0
> Reported-by: syzbot+30a35a2e9c5067cc43fa@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=30a35a2e9c5067cc43fa
> Signed-off-by: Abhishek Chauhan <quic_abchauha@quicinc.com>
> ---
> net/core/sock.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/net/core/sock.c b/net/core/sock.c
> index 8629f9aecf91..f8374be9d8c9 100644
> --- a/net/core/sock.c
> +++ b/net/core/sock.c
> @@ -1083,6 +1083,17 @@ bool sockopt_capable(int cap)
> }
> EXPORT_SYMBOL(sockopt_capable);
>
> +static int sockopt_validate_clockid(int value)
sock_txtime.clockid has type __kernel_clockid_t.
> +{
> + switch (value) {
> + case CLOCK_REALTIME:
> + case CLOCK_MONOTONIC:
> + case CLOCK_TAI:
> + return 0;
> + }
> + return -EINVAL;
> +}
> +
> /*
> * This is meant for all protocols to use and covers goings on
> * at the socket level. Everything here is generic.
> @@ -1497,6 +1508,11 @@ int sk_setsockopt(struct sock *sk, int level, int optname,
> ret = -EPERM;
> break;
> }
> +
> + ret = sockopt_validate_clockid(sk_txtime.clockid);
> + if (ret)
> + break;
> +
> sock_valbool_flag(sk, SOCK_TXTIME, true);
> sk->sk_clockid = sk_txtime.clockid;
> sk->sk_txtime_deadline_mode =
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-05-29 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 22:49 [PATCH net] net: validate SO_TXTIME clockid coming from userspace Abhishek Chauhan
2024-05-29 1:15 ` Martin KaFai Lau
2024-05-29 3:32 ` Abhishek Chauhan (ABC)
2024-05-29 13:58 ` Willem de Bruijn [this message]
2024-05-29 15:49 ` Abhishek Chauhan (ABC)
2024-05-29 16:00 ` Willem de Bruijn
2024-05-29 16:04 ` Abhishek Chauhan (ABC)
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=665734886e2a9_31b2672946e@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).