linux-kernel - Re: [PATCH] Revert "Bluetooth: Always enable management interface"

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: <20120329.003950.997517954860580620.davem@davemloft.net>
Date:	Thu, 29 Mar 2012 00:39:50 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	marcel@...tmann.org
Cc:	keithp@...thp.com, gustavo@...ovan.org,
	linux-kernel@...r.kernel.org, linux-bluetooth@...r.kernel.org,
	johan.hedberg@...el.com
Subject: Re: [PATCH] Revert "Bluetooth: Always enable management interface"

From: Marcel Holtmann <marcel@...tmann.org>
Date: Thu, 29 Mar 2012 05:33:42 +0200

> I think we actually have a broken user space in this case. I do have a
> hunch on what went wrong. It is not the kernel's fault here.

I call bullshit.

It doesn't matter what userspace is doing, "broken" or however you
want to call it.  The bluez on everyone's computer broke because of
the kernel change.

Therefore you must revert the kernel change or modify it so that
existing userland continues to work properly.

There is no other proper course of action.

And to think, I gave you bluetooth guys shit because of coding style
problems, that appears to have been just the tip of the iceberg.
--
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/