[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85b9ab27-ec57-647b-4c92-1afb9b595a2a@suse.cz>
Date: Mon, 1 Oct 2018 22:21:14 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Pavel Machek <pavel@....cz>, Steven Rostedt <rostedt@...dmis.org>
Cc: Daniel Wang <wonderfly@...gle.com>, stable@...r.kernel.org,
pmladek@...e.com, Alexander.Levin@...rosoft.com,
akpm@...ux-foundation.org, byungchul.park@....com,
dave.hansen@...el.com, hannes@...xchg.org, jack@...e.cz,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
mathieu.desnoyers@...icios.com, mgorman@...e.de, mhocko@...nel.org,
penguin-kernel@...ove.SAKURA.ne.jp, peterz@...radead.org,
tj@...nel.org, torvalds@...ux-foundation.org,
xiyou.wangcong@...il.com, pfeiner@...gle.com
Subject: Re: 4.14 backport request for dbdda842fe96f: "printk: Add console
owner and waiter logic to load balance console writes"
On 10/1/18 10:13 PM, Pavel Machek wrote:
>
> Dunno. Is the patch perhaps a bit too complex? This is not exactly
> trivial bugfix.
>
> pavel@duo:/data/l/clean-cg$ git show dbdda842fe96f | diffstat
> printk.c | 108
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>
> I see that it is pretty critical to Daniel, but maybe kernel with
> console locking redone should no longer be called 4.4?
In that case it probably should no longer be called 4.4 since at least
Meltdown/Spectre fixes :)
Powered by blists - more mailing lists