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] [thread-next>] [day] [month] [year] [list]
Message-ID: <2744142.1767879733@warthog.procyon.org.uk>
Date: Thu, 08 Jan 2026 13:42:13 +0000
From: David Howells <dhowells@...hat.com>
To: syzbot <syzbot+6182afad5045e6703b3d@...kaller.appspotmail.com>
Cc: dhowells@...hat.com, davem@...emloft.net, edumazet@...gle.com,
    horms@...nel.org, kuba@...nel.org, linux-afs@...ts.infradead.org,
    linux-kernel@...r.kernel.org, marc.dionne@...istor.com,
    netdev@...r.kernel.org, pabeni@...hat.com,
    syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [afs?] [net?] KCSAN: data-race in rxrpc_peer_keepalive_worker / rxrpc_send_data_packet

I think that this shouldn't be a problem.  The write is:

	conn->peer->last_tx_at = ktime_get_seconds();

and the read is:

	keepalive_at = peer->last_tx_at + RXRPC_KEEPALIVE_TIME;

an approximate time is fine as we're estimating when to send a keepalive
packet if we haven't transmitted a packet in a while.

David


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ