From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Bluetooth fixes for 2.6.20-rc5
Date: Mon, 22 Jan 2007 22:42:14 +0100 [thread overview]
Message-ID: <1169502134.27023.24.camel@violet> (raw)
Hi Dave,
here are two additional fixes for the Bluetooth subsystem that should go
in before the final 2.6.20 release. It was possible that the well known
PSM could be bound by anybody. That should not be possible like TCP/IP
ports below 1024 are also restricted. The other one is a simple endian
fix. Please forward them to Linus as soon as possible.
Regards
Marcel
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git
This will update the following files:
net/bluetooth/l2cap.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
through these ChangeSets:
Commit: 847641d7db15ac3f18b3d4aa05479812abdf397a
Author: Marcel Holtmann <marcel@holtmann.org> Mon, 22 Jan 2007 22:00:45 +0100
[Bluetooth] Restrict well known PSM to privileged users
The PSM values below 0x1001 of L2CAP are reserved for well known
services. Restrict the possibility to bind them to privileged
users.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Commit: 7386397636d49cd5f03da29432467d3e98cbad35
Author: Marcel Holtmann <marcel@holtmann.org> Mon, 22 Jan 2007 22:00:40 +0100
[Bluetooth] Missing endian swapping for L2CAP socket list
The PSM value in the L2CAP socket list must be converted to host
order before printing it.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
next reply other threads:[~2007-01-22 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 21:42 Marcel Holtmann [this message]
2007-01-24 6:03 ` Bluetooth fixes for 2.6.20-rc5 David Miller
2007-01-24 7:38 ` Marcel Holtmann
2007-01-24 6:44 ` David Miller
2007-01-24 8:33 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1169502134.27023.24.camel@violet \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.