From: syzbot <syzbot+09329bd987ebca21bced@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel stack overflow in sock_close
Date: Sun, 11 Dec 2022 18:43:18 -0800 [thread overview]
Message-ID: <00000000000049586705ef987729@google.com> (raw)
In-Reply-To: <20221212020158.2902-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+09329bd987ebca21bced@syzkaller.appspotmail.com
Tested on:
commit: 830b3c68 Linux 6.1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=140d36b7880000
kernel config: https://syzkaller.appspot.com/x/.config?x=738c28d3ea17d420
dashboard link: https://syzkaller.appspot.com/bug?extid=09329bd987ebca21bced
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=153c5f2f880000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-12-12 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221212020158.2902-1-hdanton@sina.com>
2022-12-12 2:43 ` syzbot [this message]
[not found] <20221211142633.2817-1-hdanton@sina.com>
2022-12-11 14:57 ` [syzbot] kernel stack overflow in sock_close syzbot
[not found] <20221211124724.2716-1-hdanton@sina.com>
2022-12-11 13:06 ` syzbot
[not found] <20221211025742.2396-1-hdanton@sina.com>
2022-12-11 10:52 ` syzbot
[not found] <20221210130803.2147-1-hdanton@sina.com>
2022-12-10 18:36 ` syzbot
[not found] <20221208124151.8280-1-hdanton@sina.com>
2022-12-08 22:30 ` syzbot
[not found] <20221208111054.8178-1-hdanton@sina.com>
2022-12-08 11:40 ` syzbot
2022-12-08 10:05 syzbot
2022-12-09 13:15 ` Mark Rutland
[not found] ` <20221209133214.1934-1-hdanton@sina.com>
2022-12-09 14:19 ` Mark Rutland
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=00000000000049586705ef987729@google.com \
--to=syzbot+09329bd987ebca21bced@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox