public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: Reminder: 1 open syzbot bug in sound subsystem
Date: Wed, 24 Jul 2019 08:56:47 -0700	[thread overview]
Message-ID: <20190724155647.GA673@sol.localdomain> (raw)
In-Reply-To: <s5hd0hzvrit.wl-tiwai@suse.de>

On Wed, Jul 24, 2019 at 09:08:26AM +0200, Takashi Iwai wrote:
> On Wed, 24 Jul 2019 04:47:23 +0200,
> Eric Biggers wrote:
> > 
> > [This email was generated by a script.  Let me know if you have any suggestions
> > to make it better, or if you want it re-generated with the latest status.]
> > 
> > Of the currently open syzbot reports against the upstream kernel, I've manually
> > marked 1 of them as possibly being a bug in the sound subsystem.
> > 
> > If you believe this bug is no longer valid, please close the syzbot report by
> > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the
> > original thread, as explained at https://goo.gl/tpsmEJ#status
> > 
> > If you believe I misattributed this bug to the sound subsystem, please let me
> > know, and if possible forward the report to the correct people or mailing list.
> > 
> > Here is the bug:
> > 
> > --------------------------------------------------------------------------------
> > Title:              KASAN: use-after-free Read in wake_up_if_idle
> > Last occurred:      131 days ago
> > Reported:           267 days ago
> > Branches:           Mainline and others
> > Dashboard link:     https://syzkaller.appspot.com/bug?id=b1e300cd7b124fc83dd4199d4d1df26310111b0f
> > Original thread:    https://lkml.kernel.org/lkml/00000000000066ab7105795f245e@google.com/T/#u
> 
> This one doesn't look like a bug that is directly related with the
> sound stuff.  Although it was triggered from a sound ioctl, UAF is
> seen rather in a notifier chain of other component.
> 
> 
> thanks,
> 
> Takashi
> 

Okay, I'm not sure what to do with this bug though.  I'll mark it as unknown
subsystem for now.

By the way, thanks for addressing all the syzbot reports in the sound subsystem!

- Eric

      reply	other threads:[~2019-07-24 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24  2:47 Reminder: 1 open syzbot bug in sound subsystem Eric Biggers
2019-07-24  7:08 ` Takashi Iwai
2019-07-24 15:56   ` Eric Biggers [this message]

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=20190724155647.GA673@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox