linux-kernel - [syzbot] INFO: timekeeping: Cycle offset (ADDR) is larger than the 'riscv_clocksource' clock's NUM% safety margin (ADDR)

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 for Android: free password hash cracker in your pocket

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

Date:   Sun, 10 Oct 2021 18:55:24 -0700
From:   syzbot <syzbot+d020c26c953f9819f97d@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] INFO: timekeeping: Cycle offset (ADDR) is larger than the
 'riscv_clocksource' clock's NUM% safety margin (ADDR)

Hello,

syzbot found the following issue on:

HEAD commit:    3ef6ca4f354c checksyscalls: Unconditionally ignore fstat{,..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=103dd877300000
kernel config:  https://syzkaller.appspot.com/x/.config?x=71a13f26e98bd7ef
dashboard link: https://syzkaller.appspot.com/bug?extid=d020c26c953f9819f97d
compiler:       riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
userspace arch: riscv64

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d020c26c953f9819f97d@...kaller.appspotmail.com

INFO: timekeeping: Cycle offset (5362492294) is larger than the 'riscv_clocksource' clock's 50% safety margin (4952755080)
      timekeeping: Your kernel is still fine, but is feeling a bit nervous

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.