netdev - Re: [PATCH 0/7] IPv4/IPv6 unregistration deadlock fixes

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: <20090518.221637.98842683.davem@davemloft.net>
Date:	Mon, 18 May 2009 22:16:37 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ebiederm@...ssion.com
Cc:	netdev@...r.kernel.org, herbert@...dor.apana.org.au,
	shemminger@...tta.com, greearb@...delatech.com, kaber@...sh.net
Subject: Re: [PATCH 0/7] IPv4/IPv6 unregistration deadlock fixes

From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Wed, 13 May 2009 19:53:40 -0700

> A while ago it was noticed that unregistering network devices could cause
> deadlocks if virtual files that take the rtnl_lock were accessed at the
> wrong time.
> 
> After looking at the different possibilities the only way to solve it
> cleanly without some kind of busy loop appears to be reducing the scope
> of the rtnl lock.
> 
> I have not tackled the hard fix yet but I have tested our current work
> around and it does not succeed in restarting the system call and
> instead leaks -ERESTARNOSYS to userspace, because we do not have a
> signal pending.
> 
> Further the current work around misses several interesting places
> in the network stack where the deadlock can occur.
> 
> I have addressed the problems by making a common helper function
> and patching all of the places I could find that had this problem.

I've added these changes to net-next-2.6, thanks.

I really can't justify sticking this into net-2.6, especially
this late in the series, sorry.
--
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