public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d020c26c953f9819f97d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] INFO: timekeeping: Cycle offset (ADDR) is larger than the 'riscv_clocksource' clock's NUM% safety margin (ADDR)
Date: Sun, 10 Oct 2021 18:55:24 -0700	[thread overview]
Message-ID: <000000000000be96b305ce0a05cc@google.com> (raw)

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@syzkaller.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@googlegroups.com.

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

                 reply	other threads:[~2021-10-11  1:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=000000000000be96b305ce0a05cc@google.com \
    --to=syzbot+d020c26c953f9819f97d@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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