From: syzbot <syzbot+a0e6f8738b58f7654417@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in sk_stream_kill_queues (8)
Date: Fri, 01 Jul 2022 07:42:09 -0700 [thread overview]
Message-ID: <000000000000142f6305e2bf64fd@google.com> (raw)
In-Reply-To: <20220701071434.1226-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a0e6f8738b58f7654417@syzkaller.appspotmail.com
Tested on:
commit: aab35c3d Add linux-next specific files for 20220627
git tree: http://kernel.source.codeaurora.cn/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=10deb7e0080000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a874f114a1e4a6b
dashboard link: https://syzkaller.appspot.com/bug?extid=a0e6f8738b58f7654417
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=1450de24080000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-07-01 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220701071434.1226-1-hdanton@sina.com>
2022-07-01 14:42 ` syzbot [this message]
[not found] <20220701032313.1164-1-hdanton@sina.com>
2022-07-01 3:41 ` [syzbot] WARNING in sk_stream_kill_queues (8) syzbot
2022-06-29 17:41 syzbot
2022-06-29 17:45 ` Eric Dumazet
2022-06-29 17:46 ` Eric Dumazet
2022-06-29 18:13 ` John Fastabend
2022-07-06 16:40 ` Cong Wang
2022-07-07 18:38 ` Cong Wang
2022-07-07 18:49 ` Stanislav Fomichev
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=000000000000142f6305e2bf64fd@google.com \
--to=syzbot+a0e6f8738b58f7654417@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.