netdev - Re: pull-request: bluetooth-2.6 2010-09-27

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: <20100927.200016.226762808.davem@davemloft.net>
Date:	Mon, 27 Sep 2010 20:00:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	padovan@...fusion.mobi
Cc:	linville@...driver.com, marcel@...tmann.org,
	linux-bluetooth@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: pull-request: bluetooth-2.6 2010-09-27

From: "Gustavo F. Padovan" <padovan@...fusion.mobi>
Date: Mon, 27 Sep 2010 23:30:35 -0300

> And a fix for a deadlock issue between the sk_sndbuf and the backlog
> queue in ERTM. The rest are also needed bug fixes.

This fix is still under discussion.

That change effects quite a few code paths.  And when I looked
at them, I was not at all convinced that dropping the socket
lock like that is safe.

Are you sure there are no pieces of socket or socket related state
that might change under us while we drop that lock, which would thus
make the operation suddenly invalid or cause a state corruption or
crash?

You really need to audit this.
--
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