Thread (28 messages) 28 messages, 8 authors, 2016-06-14

RE: [PATCH] fbcon: warn on invalid cursor blink intervals

From: Chintakuntla, Radha <hidden>
Date: 2016-06-12 05:39:34
Also in: dri-devel, linux-fbdev, lkml

-----Original Message-----
From: Henrique de Moraes Holschuh [mailto:hmh@hmh.eng.br]
Sent: Saturday, May 28, 2016 4:49 AM
To: Scot Doyle <redacted>
Cc: Tomi Valkeinen <redacted>; Jean-Christophe Plagniol-
Villard [off-list ref]; Greg Kroah-Hartman
[off-list ref]; Jeremy Kerr [off-list ref]; Ming Lei
[off-list ref]; Daney, David [off-list ref];
Dann Frazier [off-list ref]; Peter Hurley
[off-list ref]; Pavel Machek [off-list ref]; Jonathan Liu
[off-list ref]; Alistair Popple [off-list ref]; Jean-Philippe
Brucker [off-list ref]; Chintakuntla, Radha
[off-list ref]; Jiri Slaby [off-list ref]; David
Airlie [off-list ref]; David Daney [off-list ref]; dri-
devel@lists.freedesktop.org; linux-fbdev@vger.kernel.org; Linux Kernel
Mailing List [off-list ref]; stable
[off-list ref]
Subject: Re: [PATCH] fbcon: warn on invalid cursor blink intervals

On Fri, 20 May 2016, Scot Doyle wrote:
quoted
On Fri, 20 May 2016, Jeremy Kerr wrote:
quoted
quoted
Then looks there are two fix patches acked & tested:

- the patch in this thread
- another one "[PATCH] tty: vt: Fix soft lockup in fbcon cursor
blink timer."
https://lkml.org/lkml/2016/5/17/455

So which one will be pushed to linus?
Not that it's my call, but we may want both; the first as a safety
measure to prevent an invalid cur_blink_jiffies ever being set, and the
second one to actually fix the initialisation of vc_cur_blink_ms (and
address the warning introduced by the first).
Tomi / Greg,

I'd suggest
- applying "tty: vt: Fix soft lockup in fbcon cursor blink timer." to 4.7 and
stable[4.2]
quoted
- applying "fbcon: warn on invalid cursor blink intervals" to 4.7
- ignoring "fbcon: use default if cursor blink interval is not valid"

Note: the patches don't depend on each other
I applied both recommended patches on top of 4.4.11 for testing, and they
made things a lot better here.

I suggest the second patch should be backported to stable too, might as well
fix this thing for good *and keep the door closed*.
Is this patch available on some tree so that I can point to ?
And hope it will make it to linux-next soon ?
--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help