[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c7b2238de7d7232aa1d45e106654f46@nuclearcat.com>
Date: Fri, 23 Feb 2018 12:54:09 +0200
From: Denys Fedoryshchenko <nuclearcat@...learcat.com>
To: Guillaume Nault <g.nault@...halink.fr>
Cc: Cong Wang <xiyou.wangcong@...il.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
netdev-owner@...r.kernel.org
Subject: Re: ppp/pppoe, still panic 4.15.3 in ppp_push
On 2018-02-23 12:07, Guillaume Nault wrote:
> On Fri, Feb 23, 2018 at 11:41:43AM +0200, Denys Fedoryshchenko wrote:
>> On 2018-02-23 11:38, Guillaume Nault wrote:
>> > On Thu, Feb 22, 2018 at 08:51:19PM +0200, Denys Fedoryshchenko wrote:
>> > > I'm using accel-ppp that has unit-cache option, i guess for
>> > > "reusing" ppp
>> > > interfaces (because creating a lot of interfaces on BRAS with 8k
>> > > users quite
>> > > expensive).
>> > > Maybe it is somehow related and can be that scenario causing this bug?
>> > >
>> > Indeed, it'd be interesting to know if unit-cache is part of the
>> > equation (if it's workable for you to disable it).
>> Already did that and testing, unfortunately i had to disable KASAN and
>> full
>> refcount, as performance hit is too heavy for me. I will try to enable
>> KASAN
>> alone tomorrow.
>>
> Don't hesitate to post the result even if you can't afford enabling
> KASAN.
For sure, i am expecting it to crash even if KASAN not enabled (just i
wont have clean message what is reason).
Usually it happened for me within 6-10 hours after upgrade at night,
when load started to increase, i prefer to wait
48h at least, even if no crash.
Powered by blists - more mailing lists