On Wed, Dec 12, 2018 at 03:28:41PM +0900, Sergey Senozhatsky wrote:
On (12/11/18 22:08), Daniel Wang wrote:
I've been meaning to try it but kept getting distracted by other
things. I'll try to find some time for it this week or next. Right now
my intent is to get Steven's patch into 4.14 stable as it evidently
fixed the particular issue I was seeing, and as Steven said it has
been in upstream since 4.16 so it's not like backporting it will raise
any red flags. I will start another thread on -stable for it.
OK.
> I guess we still don't have a really clear understanding of what exactly
is going in your system
I would also like to get to the bottom of it. Unfortunately I haven't
got the expertise in this area nor the time to do it yet. Hence the
intent to take a step back and backport Steven's patch to fix the
issue that has resurfaced in our production recently.
No problem.
I just meant that -stable people can be a bit "unconvinced".
The -stable people tried adding this patch back in April, but ended up
getting complaints up the wazoo (https://lkml.org/lkml/2018/4/9/154)
about how this is not -stable material.
So yes, testing/acks welcome :)
--
Thanks,
Sasha
