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: <1387233731.19078.254.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Mon, 16 Dec 2013 14:42:11 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Eric Dumazet <edumazet@...gle.com>,
	Shawn Bohrer <sbohrer@...advisors.com>,
	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [RFC] udp: ipv4: fix potential deadlock on sk_dst_lock

On Mon, 2013-12-16 at 23:37 +0100, Jiri Kosina wrote:
> Commit 975022310 ("udp: ipv4: must add synchronization in 
> udp_sk_rx_dst_set()) caused sk_dst_lock to be obtained in udp4 receive 
> path, which is happening in softirq context.
> 
> inet_bind() is taking sk_dst_lock (through sk_dst_reset()) without turning 
> IRQs off, which results in the lockdep splat below.
> 
> Fix that by disabling IRQs while taking the lock in sk_dst_reset().



Thanks but I posted this fix instead :

 http://patchwork.ozlabs.org/patch/301382/




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ