From: <gregkh@linuxfoundation.org>
To: tiwai@suse.de, dvyukov@google.com, gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "ALSA: hrtimer: Fix stall by hrtimer_cancel()" has been added to the 4.1-stable tree
Date: Mon, 25 Jan 2016 16:52:46 -0800 [thread overview]
Message-ID: <145376956618896@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
ALSA: hrtimer: Fix stall by hrtimer_cancel()
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
alsa-hrtimer-fix-stall-by-hrtimer_cancel.patch
and it can be found in the queue-4.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 2ba1fe7a06d3624f9a7586d672b55f08f7c670f3 Mon Sep 17 00:00:00 2001
From: Takashi Iwai <tiwai@suse.de>
Date: Mon, 18 Jan 2016 13:52:47 +0100
Subject: ALSA: hrtimer: Fix stall by hrtimer_cancel()
From: Takashi Iwai <tiwai@suse.de>
commit 2ba1fe7a06d3624f9a7586d672b55f08f7c670f3 upstream.
hrtimer_cancel() waits for the completion from the callback, thus it
must not be called inside the callback itself. This was already a
problem in the past with ALSA hrtimer driver, and the early commit
[fcfdebe70759: ALSA: hrtimer - Fix lock-up] tried to address it.
However, the previous fix is still insufficient: it may still cause a
lockup when the ALSA timer instance reprograms itself in its callback.
Then it invokes the start function even in snd_timer_interrupt() that
is called in hrtimer callback itself, results in a CPU stall. This is
no hypothetical problem but actually triggered by syzkaller fuzzer.
This patch tries to fix the issue again. Now we call
hrtimer_try_to_cancel() at both start and stop functions so that it
won't fall into a deadlock, yet giving some chance to cancel the queue
if the functions have been called outside the callback. The proper
hrtimer_cancel() is called in anyway at closing, so this should be
enough.
Reported-and-tested-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
sound/core/hrtimer.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/sound/core/hrtimer.c
+++ b/sound/core/hrtimer.c
@@ -90,7 +90,7 @@ static int snd_hrtimer_start(struct snd_
struct snd_hrtimer *stime = t->private_data;
atomic_set(&stime->running, 0);
- hrtimer_cancel(&stime->hrt);
+ hrtimer_try_to_cancel(&stime->hrt);
hrtimer_start(&stime->hrt, ns_to_ktime(t->sticks * resolution),
HRTIMER_MODE_REL);
atomic_set(&stime->running, 1);
@@ -101,6 +101,7 @@ static int snd_hrtimer_stop(struct snd_t
{
struct snd_hrtimer *stime = t->private_data;
atomic_set(&stime->running, 0);
+ hrtimer_try_to_cancel(&stime->hrt);
return 0;
}
Patches currently in stable-queue which might be from tiwai@suse.de are
queue-4.1/alsa-hrtimer-fix-stall-by-hrtimer_cancel.patch
queue-4.1/alsa-hda-fix-white-noise-on-dell-latitude-e5550.patch
queue-4.1/alsa-hda-fix-the-headset-mic-detection-problem-for-a-dell-laptop.patch
queue-4.1/alsa-timer-harden-slave-timer-list-handling.patch
queue-4.1/alsa-timer-fix-double-unlink-of-active_list.patch
queue-4.1/alsa-hda-add-fixup-for-acer-aspire-one-cloudbook-14.patch
queue-4.1/alsa-control-avoid-kernel-warnings-from-tlv-ioctl-with-numid-0.patch
queue-4.1/alsa-hda-flush-the-pending-probe-work-at-remove.patch
queue-4.1/alsa-usb-audio-add-sample-rate-inquiry-quirk-for-audioquest-dragonfly.patch
queue-4.1/alsa-hda-apply-hp-headphone-fixups-more-generically.patch
queue-4.1/alsa-hda-set-codec-to-d3-at-reboot-shutdown-on-thinkpads.patch
queue-4.1/alsa-hda-realtek-fix-silent-headphone-output-on-macpro-4-1-v2.patch
queue-4.1/alsa-rme96-fix-unexpected-volume-reset-after-rate-changes.patch
queue-4.1/alsa-fireworks-bebob-oxfw-dice-enable-to-make-as-built-in.patch
queue-4.1/alsa-hda-set-skl-hda-controller-power-at-freeze-and-thaw.patch
queue-4.1/alsa-hda-add-inverted-dmic-for-packard-bell-dots.patch
queue-4.1/alsa-usb-add-native-dsd-support-for-oppo-ha-1.patch
queue-4.1/alsa-hda-add-intel-lewisburg-device-ids-audio.patch
queue-4.1/alsa-hda-add-a-fixup-for-thinkpad-x1-carbon-2nd.patch
queue-4.1/alsa-seq-fix-race-at-timer-setup-and-close.patch
queue-4.1/alsa-pcm-fix-snd_pcm_hw_params-struct-copy-in-compat-mode.patch
queue-4.1/alsa-seq-fix-snd_seq_call_port_info_ioctl-in-compat-mode.patch
queue-4.1/alsa-hda-disable-64bit-address-for-creative-hda-controllers.patch
queue-4.1/alsa-seq-fix-missing-null-check-at-remove_events-ioctl.patch
queue-4.1/alsa-usb-audio-fix-mixer-ctl-regression-of-native-instrument-devices.patch
queue-4.1/alsa-usb-audio-add-a-more-accurate-volume-quirk-for-audioquest-dragonfly.patch
queue-4.1/alsa-hda-fix-noise-problems-on-thinkpad-t440s.patch
queue-4.1/alsa-timer-handle-disconnection-more-safely.patch
queue-4.1/alsa-hda-fix-bass-pin-fixup-for-asus-n550jx.patch
queue-4.1/alsa-timer-fix-race-among-timer-ioctls.patch
queue-4.1/alsa-hda-apply-pin-fixup-for-hp-probook-6550b.patch
queue-4.1/alsa-hda-apply-click-noise-workaround-for-thinkpads-generically.patch
queue-4.1/alsa-hda-fix-noise-on-gigabyte-z170x-mobo.patch
reply other threads:[~2016-01-26 0:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=145376956618896@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dvyukov@google.com \
--cc=stable-commits@vger.kernel.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.