From: syzbot <syzbot+e29d28728f38190cecfc@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in snd_pcm_post_stop
Date: Tue, 17 Jan 2023 23:06:22 -0800 [thread overview]
Message-ID: <0000000000002fbfee05f2847467@google.com> (raw)
In-Reply-To: <20230118055330.2780-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in io_ring_exit_work
------------[ cut here ]------------
WARNING: CPU: 1 PID: 75 at io_uring/io_uring.c:2977 io_ring_exit_work+0x320/0xc80 io_uring/io_uring.c:2977
Modules linked in:
CPU: 0 PID: 75 Comm: kworker/u4:4 Not tainted 6.2.0-rc3-next-20230112-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x320/0xc80 io_uring/io_uring.c:2977
Code: 40 8c e8 57 f4 02 f8 48 8b 05 f0 59 74 02 31 ff 4c 8b 74 24 10 49 29 c6 4c 89 f6 e8 8e 21 b5 f7 4d 85 f6 79 10 e8 b4 24 b5 f7 <0f> 0b 48 c7 44 24 08 70 17 00 00 e8 a4 24 b5 f7 48 8b 74 24 08 48
RSP: 0018:ffffc900020afbd0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88807e004838 RCX: 0000000000000000
RDX: ffff888018ca57c0 RSI: ffffffff89cc982c RDI: 0000000000000007
RBP: ffff88807e004000 R08: 0000000000000007 R09: 0000000000000000
R10: fffffffffffffff9 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff88807e004040 R14: fffffffffffffff9 R15: ffff88807e0043c8
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a8f42b70c0 CR3: 000000000c571000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work+0x9bf/0x1750 kernel/workqueue.c:2293
worker_thread+0x669/0x1090 kernel/workqueue.c:2440
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Tested on:
commit: 0a093b28 Add linux-next specific files for 20230112
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=111bfc46480000
kernel config: https://syzkaller.appspot.com/x/.config?x=835f3591019836d5
dashboard link: https://syzkaller.appspot.com/bug?extid=e29d28728f38190cecfc
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=111aca96480000
next parent reply other threads:[~2023-01-18 7:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230118055330.2780-1-hdanton@sina.com>
2023-01-18 7:06 ` syzbot [this message]
[not found] <20230201233318.593-1-hdanton@sina.com>
2023-02-02 5:24 ` [syzbot] KASAN: use-after-free Read in snd_pcm_post_stop syzbot
[not found] <20230119081633.3470-1-hdanton@sina.com>
2023-02-01 16:41 ` syzbot
[not found] <20230119030102.3388-1-hdanton@sina.com>
2023-01-19 3:18 ` syzbot
[not found] <20230119012145.3304-1-hdanton@sina.com>
2023-01-19 2:01 ` syzbot
[not found] <20230118222858.3127-1-hdanton@sina.com>
2023-01-19 1:13 ` syzbot
[not found] <20230118150448.3071-1-hdanton@sina.com>
2023-01-18 15:27 ` syzbot
[not found] <20230118094915.2906-1-hdanton@sina.com>
2023-01-18 14:07 ` syzbot
[not found] <20230118023942.2716-1-hdanton@sina.com>
2023-01-18 2:59 ` syzbot
[not found] <20230117093837.2433-1-hdanton@sina.com>
2023-01-17 17:54 ` syzbot
[not found] <20230117015907.2238-1-hdanton@sina.com>
2023-01-17 2:39 ` syzbot
[not found] <20230116053340.1952-1-hdanton@sina.com>
2023-01-16 12:44 ` syzbot
[not found] <20230116012417.1876-1-hdanton@sina.com>
2023-01-16 1:55 ` syzbot
[not found] <20230116000718.1809-1-hdanton@sina.com>
2023-01-16 0:34 ` syzbot
[not found] <20230115232650.1752-1-hdanton@sina.com>
2023-01-15 23:43 ` syzbot
[not found] <20230115220938.1677-1-hdanton@sina.com>
2023-01-15 22:31 ` syzbot
[not found] <20230115122106.1614-1-hdanton@sina.com>
2023-01-15 16:04 ` syzbot
[not found] <20230115074631.1541-1-hdanton@sina.com>
2023-01-15 8:06 ` syzbot
[not found] <20230113113404.879-1-hdanton@sina.com>
2023-01-13 11:59 ` syzbot
2023-01-13 7:30 syzbot
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=0000000000002fbfee05f2847467@google.com \
--to=syzbot+e29d28728f38190cecfc@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.