netdev - Re: Lockdep splat for rt8169

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] [day] [month] [year] [list]

Date:	Sat, 7 May 2011 20:15:58 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Ben Greear <greearb@...delatech.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: Lockdep splat for rt8169

Ben Greear <greearb@...delatech.com> :
[...]
> Seems to be the first post 2.6.38 kernel that will boot stable
> on this system!

You are spoiled. I have to merge davem-next with -git or my raid1
test machine is unusable. :o/

> I previously reported the timer issue, but perhaps the lock
> debugging will help.

It is the same problem and will be triggered by any driver changing
the link state from an hard irq context - the r8169 driver is not
alone.

If you want a q'n'd workaround for the r8169 driver, defering its
LinkChg processing from the irq handler to a work task may do the
trick.

I am not sure what the general fix is:
- do more or less the same for linkwatch (i.e. defer more work to
  a user context)
- audit each driver
- ???

-- 
Ueimor
--
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