diff options
| author | Abhishek Chauhan <[email protected]> | 2024-05-29 11:31:30 -0700 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2024-06-01 15:47:23 -0700 |
| commit | 73451e9aaa24e8e44cb91e5fd6b59bf53e069c1f (patch) | |
| tree | 26f3749d9df7671333331b8b359055abeb2cb2c6 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | d1f9e6513e4e64215c7a2a31476032c0c9107a23 (diff) | |
net: validate SO_TXTIME clockid coming from userspace
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/[email protected]/
Link: https://lore.kernel.org/lkml/[email protected]/
Fixes: 1693c5db6ab8 ("net: Add additional bit to support clockid_t timestamp type")
Reported-by: [email protected]
Closes: https://syzkaller.appspot.com/bug?extid=d7b227731ec589e7f4f0
Reported-by: [email protected]
Closes: https://syzkaller.appspot.com/bug?extid=30a35a2e9c5067cc43fa
Signed-off-by: Abhishek Chauhan <[email protected]>
Acked-by: Martin KaFai Lau <[email protected]>
Reviewed-by: Willem de Bruijn <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions