From: syzbot <syzbot+c0998868487c1f7e05e5@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in process_one_work
Date: Tue, 07 Feb 2023 00:50:17 -0800 [thread overview]
Message-ID: <000000000000a01e8305f4183c3b@google.com> (raw)
In-Reply-To: <20230207082506.1322-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+c0998868487c1f7e05e5@syzkaller.appspotmail.com
Tested on:
commit: 4fafd969 Add linux-next specific files for 20230203
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1753218d480000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d2fba7d42502ca4
dashboard link: https://syzkaller.appspot.com/bug?extid=c0998868487c1f7e05e5
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=15a33033480000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-02-07 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207082506.1322-1-hdanton@sina.com>
2023-02-07 8:50 ` syzbot [this message]
[not found] <20230207072656.1175-1-hdanton@sina.com>
2023-02-07 7:43 ` [syzbot] kernel BUG in process_one_work syzbot
[not found] <20230207045013.1083-1-hdanton@sina.com>
2023-02-07 5:12 ` syzbot
[not found] <20230207032427.1028-1-hdanton@sina.com>
2023-02-07 3:41 ` syzbot
[not found] <20230207023236.975-1-hdanton@sina.com>
2023-02-07 2:47 ` syzbot
[not found] <20230207002846.844-1-hdanton@sina.com>
2023-02-07 1:09 ` syzbot
[not found] <20230206140214.1911-1-hdanton@sina.com>
2023-02-06 17:15 ` syzbot
2023-02-06 9:23 syzbot
2023-02-07 14:16 ` David Howells
2023-02-07 14:50 ` syzbot
2023-02-07 15:09 ` David Howells
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=000000000000a01e8305f4183c3b@google.com \
--to=syzbot+c0998868487c1f7e05e5@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.