netdev - Re: [patch v2] bluetooth: handle l2cap_create_connless

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: <20100426.111259.112594696.davem@davemloft.net>
Date:	Mon, 26 Apr 2010 11:12:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	gustavo@...ovan.org
Cc:	error27@...il.com, marcel@...tmann.org,
	andrei.emeltchenko@...ia.com, linux-bluetooth@...r.kernel.org,
	netdev@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [patch v2] bluetooth: handle l2cap_create_connless_pdu() errors

From: "Gustavo F. Padovan" <gustavo@...ovan.org>
Date: Mon, 26 Apr 2010 12:09:19 -0300

> Hi Dan,
> 
> * Dan Carpenter <error27@...il.com> [2010-04-26 13:36:27 +0200]:
> 
>> l2cap_create_connless_pdu() can sometimes return ERR_PTR(-ENOMEM) or
>> ERR_PTR(-EFAULT).
>> 
>> Signed-off-by: Dan Carpenter <error27@...il.com>
>> ---
>> In v2 I wrote the patch on top of Gustavo Padovon's devel tree

This is the kind of bug that could cause a crash if the path actually
executes.

Therefore it tires me that that submitter was told to regenerate this
patch against some devel tree that is -next bound, when in fact this
is the kind of fix that warrants inclusion right now into net-2.6

Marcel, please do whatever magic you need to so I can get this into
Linus's tree as I did the rest of the ERR_PTR() fixes from Dan already.
No reason to treat Bluetooth special and defer these fixes to -next.

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