From: syzbot <syzbot+0bc015ebddc291a97116@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [virt?] [io-uring?] [kvm?] BUG: soft lockup in vsock_connect
Date: Fri, 24 Mar 2023 04:07:23 -0700 [thread overview]
Message-ID: <000000000000d1686905f7a3655a@google.com> (raw)
In-Reply-To: <20230324104205.1646-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+0bc015ebddc291a97116@syzkaller.appspotmail.com
Tested on:
commit: fff5a5e7 Merge tag 'for-linus' of git://git.armlinux.o..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=133635eec80000
kernel config: https://syzkaller.appspot.com/x/.config?x=12e37aa0abf8dee
dashboard link: https://syzkaller.appspot.com/bug?extid=0bc015ebddc291a97116
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1478e85ac80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-03-24 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230324104205.1646-1-hdanton@sina.com>
2023-03-24 11:07 ` syzbot [this message]
2023-03-24 0:52 [syzbot] [net?] [virt?] [io-uring?] [kvm?] BUG: soft lockup in vsock_connect syzbot
2023-03-24 8:38 ` Stefano Garzarella
2023-03-24 8:38 ` Stefano Garzarella
2023-03-18 0:32 ` Bobby Eshleman
2023-03-26 19:20 ` Cong Wang
2023-03-26 19:20 ` Cong Wang
2023-03-27 9:07 ` Stefano Garzarella
2023-03-27 9:07 ` Stefano Garzarella
2023-03-24 15:33 ` Stefano Garzarella
2023-03-24 15:33 ` Stefano Garzarella
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=000000000000d1686905f7a3655a@google.com \
--to=syzbot+0bc015ebddc291a97116@syzkaller.appspotmail.com \
--cc=hdanton@sina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.