netdev - Re: circular locking, mirred, 2.6.24.2

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]

Date:	Fri, 7 Mar 2008 10:48:43 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Denys Fedoryshchenko <denys@...p.net.lb>
Cc:	jamal <hadi@...erus.ca>, netdev@...r.kernel.org
Subject: Re: circular locking, mirred, 2.6.24.2

On Fri, Mar 07, 2008 at 12:19:03PM +0200, Denys Fedoryshchenko wrote:
> Ok, i will proceed and will try all required options after few hours (need to 
> go another city, work).
> I will try to set max as possible debug options.

Max could be too much, but e.g. this is sometimes helpful too:
CONFIG_DEBUG_LIST is not set

BTW, you didn't write yet if with min/no debugging, no 4KSTACKS and
lockdep off there is any change in these lockups?

And no need to hurry...

> On bug_feb.txt it is triggering ONLY lockdep warning, but full network lockup 
> occur very rarely. But even it happens with me 2 times, i am not sure it is 
> same problem. Let's stick maybe to this one (lockdep warning) which is easy 
> to reproduce.
> I will open also bugzilla report.

Send Re: here with a bugzilla number.

> 
> Regarding testing with compiled in modules, i did
> CONFIG_IFB=y 
> CONFIG_DUMMY=y
> CONFIG_BONDING=y
> CONFIG_MACVLAN=y 
> CONFIG_EQUALIZER=y
> CONFIG_TUN=y
> 
> It is still triggering lockdep.
> Here is full dmesg:
> http://www.nuclearcat.com/files/dmesg_1234.txt

OK, but it seems still without my last patch to ifb?

Thanks,
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