netdev - Re: [PATCH net-next v2] selftests: return failure when timestamps can't be reported

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <172592643426.3961170.381877473938074234.git-patchwork-notify@kernel.org>
Date: Tue, 10 Sep 2024 00:00:34 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jason Xing <kerneljasonxing@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, shuah@...nel.org, willemdebruijn.kernel@...il.com,
 willemb@...gle.com, linux-kselftest@...r.kernel.org, netdev@...r.kernel.org,
 kernelxing@...cent.com
Subject: Re: [PATCH net-next v2] selftests: return failure when timestamps can't
 be reported

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Fri,  6 Sep 2024 00:00:35 +0800 you wrote:
> From: Jason Xing <kernelxing@...cent.com>
> 
> When I was trying to modify the tx timestamping feature, I found that
> running "./txtimestamp -4 -C -L 127.0.0.1" didn't reflect the error:
> I succeeded to generate timestamp stored in the skb but later failed
> to report it to the userspace (which means failed to put css into cmsg).
> It can happen when someone writes buggy codes in __sock_recv_timestamp(),
> for example.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] selftests: return failure when timestamps can't be reported
    https://git.kernel.org/netdev/net-next/c/a7e387375f22

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html