[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJ4U8B=E7AiJ_+SSKKKFcWLEx0uD2+Dkp67CLKRX-PCDg@mail.gmail.com>
Date: Fri, 7 Apr 2017 09:03:28 -0500
From: Rob Herring <robh@...nel.org>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Michael Neuling <mikey@...ling.org>,
Al Viro <viro@...iv.linux.org.uk>,
johan Hovold <johan@...nel.org>,
Peter Hurley <peter@...leysoftware.com>,
Wang YanQing <udknight@...il.com>,
Alexander Popov <alex.popov@...ux.com>,
Mikulas Patocka <mpatocka@...hat.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: tty crash in tty_ldisc_receive_buf()
On Thu, Apr 6, 2017 at 8:03 PM, Benjamin Herrenschmidt
<benh@...nel.crashing.org> wrote:
> On Thu, 2017-04-06 at 08:28 -0500, Rob Herring wrote:
>>
>> Can you try this one [1].
>>
>> Rob
>>
>> [1] https://lkml.org/lkml/2017/3/23/569
>
> Unless I missed something, that patch doesn't change barriers or
> locking, so I don't see how it could fix anything ...
Only because that's a code path that I changed recently and the
locking and ordering appears to be tricky.
> Mind you we haven't quite figured out exactly what's happening here.
Is this with a serial port? There were some changes to serial_core close in 4.9.
Rob
Powered by blists - more mailing lists