All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f7d9295d2565ee819d21@syzkaller.appspotmail.com>
To: alsa-devel@alsa-project.org, len.brown@intel.com,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	pavel@ucw.cz, perex@perex.cz, rjw@rjwysocki.net,
	syzkaller-bugs@googlegroups.com, tiwai@suse.com, tiwai@suse.de
Subject: Re: [syzbot] general protection fault in pm_qos_update_target
Date: Wed, 20 Apr 2022 14:28:09 -0700	[thread overview]
Message-ID: <0000000000007b1cbd05dd1cab5a@google.com> (raw)
In-Reply-To: <0000000000004ecea505c28504b9@google.com>

syzbot suspects this issue was fixed by commit:

commit 3c3201f8c7bb77eb53b08a3ca8d9a4ddc500b4c0
Author: Takashi Iwai <tiwai@suse.de>
Date:   Tue Mar 22 17:07:19 2022 +0000

    ALSA: pcm: Fix races among concurrent prepare and hw_params/hw_free calls

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=104e3034f00000
start commit:   dbb5afad100a ptrace: make ptrace() fail if the tracee chan..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=91ff0467ce169bc
dashboard link: https://syzkaller.appspot.com/bug?extid=f7d9295d2565ee819d21
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16c75e73d00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: ALSA: pcm: Fix races among concurrent prepare and hw_params/hw_free calls

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2022-04-20 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 11:37 [syzbot] general protection fault in pm_qos_update_target syzbot
2022-04-20 21:28 ` syzbot [this message]
2022-04-21  8:04   ` Dmitry Vyukov
2022-04-21  8:04     ` Dmitry Vyukov

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=0000000000007b1cbd05dd1cab5a@google.com \
    --to=syzbot+f7d9295d2565ee819d21@syzkaller.appspotmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=perex@perex.cz \
    --cc=rjw@rjwysocki.net \
    --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.