From: Randy Dunlap <rdunlap@infradead.org>
To: syzbot <syzbot+f3a0fa110fd630ab56c8@syzkaller.appspotmail.com>,
anna.schumaker@netapp.com, bfields@fieldses.org,
chuck.lever@oracle.com, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
trond.myklebust@hammerspace.com
Subject: Re: UBSAN: shift-out-of-bounds in xprt_do_reserve
Date: Wed, 10 Feb 2021 16:52:18 -0800 [thread overview]
Message-ID: <258ca358-d4ea-2bc0-9b0d-1d659eec04f7@infradead.org> (raw)
In-Reply-To: <0000000000000f622105baf14335@google.com>
On 2/9/21 5:24 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: dd86e7fa Merge tag 'pci-v5.11-fixes-2' of git://git.kernel..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=105930c4d00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=266a5362c89c8127
> dashboard link: https://syzkaller.appspot.com/bug?extid=f3a0fa110fd630ab56c8
> compiler: Debian clang version 11.0.1-2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17ba3038d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15cf0d64d00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+f3a0fa110fd630ab56c8@syzkaller.appspotmail.com
#syz dup: UBSAN: shift-out-of-bounds in xprt_calc_majortimeo
> ================================================================================
> UBSAN: shift-out-of-bounds in net/sunrpc/xprt.c:658:14
> shift exponent 536870976 is too large for 64-bit type 'unsigned long'
> CPU: 1 PID: 8411 Comm: syz-executor902 Not tainted 5.11.0-rc6-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:79 [inline]
> dump_stack+0x137/0x1be lib/dump_stack.c:120
> ubsan_epilogue lib/ubsan.c:148 [inline]
> __ubsan_handle_shift_out_of_bounds+0x432/0x4d0 lib/ubsan.c:395
> xprt_calc_majortimeo net/sunrpc/xprt.c:658 [inline]
> xprt_init_majortimeo net/sunrpc/xprt.c:686 [inline]
--
~Randy
next prev parent reply other threads:[~2021-02-11 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 1:24 syzbot
2021-02-11 0:52 ` Randy Dunlap [this message]
2021-02-11 1:07 ` Trond Myklebust
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=258ca358-d4ea-2bc0-9b0d-1d659eec04f7@infradead.org \
--to=rdunlap@infradead.org \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+f3a0fa110fd630ab56c8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trond.myklebust@hammerspace.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
all inboxes | Powered by JetHome®