All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.8.y-and-older] ALSA: timer: Set lower bound of start tick time
Date: Thu, 6 Jun 2024 14:57:53 +0200	[thread overview]
Message-ID: <2024060648-truck-prototype-1292@gregkh> (raw)
In-Reply-To: <20240527062431.18709-1-tiwai@suse.de>

On Mon, May 27, 2024 at 08:23:59AM +0200, Takashi Iwai wrote:
> commit 4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e upstream.
> 
> Currently ALSA timer doesn't have the lower limit of the start tick
> time, and it allows a very small size, e.g. 1 tick with 1ns resolution
> for hrtimer.  Such a situation may lead to an unexpected RCU stall,
> where  the callback repeatedly queuing the expire update, as reported
> by fuzzer.
> 
> This patch introduces a sanity check of the timer start tick time, so
> that the system returns an error when a too small start size is set.
> As of this patch, the lower limit is hard-coded to 100us, which is
> small enough but can still work somehow.
> 
> [ backport note: the error handling is changed, as the original commit
>   is based on the recent cleanup with guard() in commit beb45974dd49
>   -- tiwai ]
> 
> Reported-by: syzbot+43120c2af6ca2938cc38@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/r/000000000000fa00a1061740ab6d@google.com
> Cc: <stable@vger.kernel.org>
> Link: https://lore.kernel.org/r/20240514182745.4015-1-tiwai@suse.de
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
> 
> Greg, this is an alternative fix to the original cherry-pick; apply
> to 6.8.y and older stable kernels.  Thanks!

Now queued up, thanks!

greg k-h

      reply	other threads:[~2024-06-06 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  6:23 [PATCH 6.8.y-and-older] ALSA: timer: Set lower bound of start tick time Takashi Iwai
2024-06-06 12:57 ` Greg Kroah-Hartman [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=2024060648-truck-prototype-1292@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --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.