From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: hverkuil-cisco@xs4all.nl, mchehab+huawei@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] media: cec: avoid decrementing transmit_queue_sz if it is 0" failed to apply to 5.5-stable tree
Date: Sun, 9 Feb 2020 13:15:15 -0500 [thread overview]
Message-ID: <20200209181515.GM3584@sasha-vm> (raw)
In-Reply-To: <15812488366474@kroah.com>
On Sun, Feb 09, 2020 at 12:47:16PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.5-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 4be77174c3fafc450527a0c383bb2034d2db6a2d Mon Sep 17 00:00:00 2001
>From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>Date: Sat, 7 Dec 2019 23:48:09 +0100
>Subject: [PATCH] media: cec: avoid decrementing transmit_queue_sz if it is 0
>
>WARN if transmit_queue_sz is 0 but do not decrement it.
>The CEC adapter will become unresponsive if it goes below
>0 since then it thinks there are 4 billion messages in the
>queue.
>
>Obviously this should not happen, but a driver bug could
>cause this.
>
>Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>Cc: <stable@vger.kernel.org> # for v4.12 and up
>Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Another duplicate commit:
4be77174c3fa ("media: cec: avoid decrementing transmit_queue_sz if it is 0")
95c29d46ab2a ("media: cec: avoid decrementing transmit_queue_sz if it is 0")
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-09 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 11:47 FAILED: patch "[PATCH] media: cec: avoid decrementing transmit_queue_sz if it is 0" failed to apply to 5.5-stable tree gregkh
2020-02-09 18:15 ` Sasha Levin [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=20200209181515.GM3584@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=mchehab+huawei@kernel.org \
--cc=stable@vger.kernel.org \
/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.