From: syzbot <syzbot+39e3268af9968f153591@syzkaller.appspotmail.com>
To: alsa-devel-owner@alsa-project.org, alsa-devel@alsa-project.org,
anthony.l.nguyen@intel.com, clemens@ladisch.de, coding@diwic.se,
colin.king@intel.com, hdanton@sina.com,
linux-kernel@vger.kernel.org, naamax.meir@linux.intel.com,
perex@perex.cz, sasha.neftin@intel.com,
syzkaller-bugs@googlegroups.com, tiwai@suse.com, tiwai@suse.de
Subject: Re: [syzbot] KASAN: use-after-free Read in snd_rawmidi_transmit
Date: Fri, 01 Jul 2022 12:21:16 -0700 [thread overview]
Message-ID: <00000000000049a18105e2c34a0c@google.com> (raw)
In-Reply-To: <000000000000915bd505ddaff576@google.com>
syzbot suspects this issue was fixed by commit:
commit 0125de38122f0f66bf61336158d12a1aabfe6425
Author: Takashi Iwai <tiwai@suse.de>
Date: Wed May 25 13:12:03 2022 +0000
ALSA: usb-audio: Cancel pending work at closing a MIDI substream
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1180b25c080000
start commit: 2a5699b0de4e Merge tag 'leds-5.19-rc1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f915857c44e13980
dashboard link: https://syzkaller.appspot.com/bug?extid=39e3268af9968f153591
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=119d1fcbf00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17716bedf00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ALSA: usb-audio: Cancel pending work at closing a MIDI substream
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-07-04 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 5:11 [syzbot] KASAN: use-after-free Read in snd_rawmidi_transmit syzbot
2022-06-01 8:37 ` syzbot
2022-06-01 15:35 ` syzbot
2022-07-01 19:21 ` syzbot [this message]
2022-07-04 7:51 ` Dmitry Vyukov
2022-07-04 7:51 ` Dmitry Vyukov
[not found] <20220601140527.4708-1-hdanton@sina.com>
2022-06-01 15:58 ` 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=00000000000049a18105e2c34a0c@google.com \
--to=syzbot+39e3268af9968f153591@syzkaller.appspotmail.com \
--cc=alsa-devel-owner@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=anthony.l.nguyen@intel.com \
--cc=clemens@ladisch.de \
--cc=coding@diwic.se \
--cc=colin.king@intel.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naamax.meir@linux.intel.com \
--cc=perex@perex.cz \
--cc=sasha.neftin@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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.