From: syzbot <syzbot+4cb9fad083898f54c517@syzkaller.appspotmail.com>
To: quic_zhonhan@quicinc.com
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
perex@perex.cz, quic_zhonhan@quicinc.com,
syzkaller-bugs@googlegroups.com, tiwai@suse.com
Subject: Re: [syzbot] [sound?] BUG: sleeping function called from invalid context in snd_card_locked
Date: Sat, 01 Mar 2025 01:26:33 -0800 [thread overview]
Message-ID: <67c2d2c9.050a0220.dc10f.0161.GAE@google.com> (raw)
In-Reply-To: <6610cdb8-072e-47fe-b9bc-f4f5b9a79f8e@quicinc.com>
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: d082ecbc71e9 Linux 6.14-rc4
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=14e3d7a4580000
> > kernel config:
> https://syzkaller.appspot.com/x/.config?x=8f2f8fb6ad08b539
> > dashboard link:
> https://syzkaller.appspot.com/bug?extid=4cb9fad083898f54c517
> > compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils
> for Debian) 2.40
>
>
> BUG: sleeping function called from invalid context and
> raw_local_irq_restore() called with IRQs enabled seems can be
> fixed by below change. if it is valid, will arise the PATCH.
>
> #syz test:
want either no args or 2 args (repo, branch), got 4
>
> diff --git a/sound/core/timer.c b/sound/core/timer.c
> index fbada79380f9..5290c1b9f2b8 100644
> --- a/sound/core/timer.c
> +++ b/sound/core/timer.c
> @@ -767,6 +767,7 @@ static void snd_timer_process_callbacks(struct
> snd_timer *timer,
> {
> struct snd_timer_instance *ti;
> unsigned long resolution, ticks;
> + unsigned long flags;
>
> while (!list_empty(head)) {
> ti = list_first_entry(head, struct snd_timer_instance,
> @@ -780,10 +781,10 @@ static void snd_timer_process_callbacks(struct
> snd_timer *timer,
> ti->pticks = 0;
> resolution = ti->resolution;
> ti->flags |= SNDRV_TIMER_IFLG_CALLBACK;
> - spin_unlock(&timer->lock);
> + spin_unlock_irqrestore(&timer->lock, flags);
> if (ti->callback)
> ti->callback(ti, resolution, ticks);
> - spin_lock(&timer->lock);
> + spin_lock_irqsave(&timer->lock, flags);
> ti->flags &= ~SNDRV_TIMER_IFLG_CALLBACK;
> }
> }
> @@ -805,14 +806,16 @@ static void snd_timer_clear_callbacks(struct
> snd_timer *timer,
> static void snd_timer_work(struct work_struct *work)
> {
> struct snd_timer *timer = container_of(work, struct snd_timer,
> task_work);
> + unsigned long flags;
>
> if (timer->card && timer->card->shutdown) {
> snd_timer_clear_callbacks(timer, &timer->sack_list_head);
> return;
> }
>
> - guard(spinlock_irqsave)(&timer->lock);
> + spin_lock_irqsave(&timer->lock, flags);
> snd_timer_process_callbacks(timer, &timer->sack_list_head);
> + spin_unlock_irqrestore(&timer->lock, flags);
> }
>
> /*
>
>
>
>
>
> Thanks
> Zhongqiu Han
next prev parent reply other threads:[~2025-03-01 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 9:25 [syzbot] [sound?] BUG: sleeping function called from invalid context in snd_card_locked Zhongqiu Han
2025-03-01 9:26 ` syzbot [this message]
2025-03-01 9:34 ` Takashi Iwai
2025-03-01 9:50 ` Zhongqiu Han
2025-03-01 10:22 ` Takashi Iwai
2025-03-01 10:43 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2025-03-01 2:37 syzbot
2025-03-01 7:53 ` Hillf Danton
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=67c2d2c9.050a0220.dc10f.0161.GAE@google.com \
--to=syzbot+4cb9fad083898f54c517@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_zhonhan@quicinc.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.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.