netdev - Re: BUG? locking issue(networking?) with latest git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200809041203.07460.denys@visp.net.lb>
Date:	Thu, 4 Sep 2008 12:03:07 +0300
From:	Denys Fedoryshchenko <denys@...p.net.lb>
To:	Jarek Poplawski <jarkao2@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: BUG? locking issue(networking?) with latest git

On Thursday 04 September 2008, Jarek Poplawski wrote:
> On 03-09-2008 13:22, Denys Fedoryshchenko wrote:
> > I am getting strange lockup, all operations (tc, ifconfig,pppd) after few
> > days running pppoe-server.
> >
> > Programgs getting blocked very strange way, i am not able to kill them
> > even. Softlockup detection enabled, lock dependencies (except lock
> > dependency engine debugging), RT mutexes and deadlock detection enabled
> > too.
> >
> > I notice this bug few weeks ago, even before latest patches, and seems it
> > still remains.
>
> Do you mean this didn't happen with some 2.6.27-rc's? (There was quite
> substantial change in ppp_generic with lock_kernel() in 2.6.27-rc1.)
I was not able to run early rc's on my pppoe's. Do you suggest to try reverse 
those changes?

> Alas it shows only some tasks waiting for locks. Maybe it's enough for
> someone with better ppp knowledge, but unless there is such a response
> I guess you should better try with PROVE_LOCKING turned on yet.
It is already turned on.
>
> Jarek P.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html