linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org, gustavo@padovan.org,
	rshaffer@codeaurora.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/5] Bluetooth: Validate PSM values in calls to connect() and bind().
Date: Tue, 10 Aug 2010 17:21:10 -0400	[thread overview]
Message-ID: <1281475270.12579.223.camel@localhost.localdomain> (raw)
In-Reply-To: <1281466850-5297-3-git-send-email-mathewm@codeaurora.org>

Hi Mat,

> Valid L2CAP PSMs are odd numbers, and the least significant bit of the
> most significant byte must be 0.
> 
> Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
> ---
>  net/bluetooth/l2cap.c |   23 +++++++++++++++++++----
>  1 files changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/net/bluetooth/l2cap.c b/net/bluetooth/l2cap.c
> index c784703..61aa961 100644
> --- a/net/bluetooth/l2cap.c
> +++ b/net/bluetooth/l2cap.c
> @@ -1008,10 +1008,19 @@ static int l2cap_sock_bind(struct socket *sock, struct sockaddr *addr, int alen)
>  		goto done;
>  	}
>  
> -	if (la.l2_psm && __le16_to_cpu(la.l2_psm) < 0x1001 &&
> -				!capable(CAP_NET_BIND_SERVICE)) {
> -		err = -EACCES;
> -		goto done;
> +	/* If specified, PSM must be odd and lsb of upper byte must be 0 */
> +	if (la.l2_psm) {
> +		__u16 psm = __le16_to_cpu(la.l2_psm);
> +

I would just put the comment here:

                  /* PSM must be odd and lsb of upper byte must be 0 */
> +		if ((psm & 0x0101) != 0x0001) {
> +			err = -EINVAL;
> +			goto done;
> +		}

And then while you at it:

                  /* Restrict usage of well known PSMs */
> +		if (psm < 0x1001 && !capable(CAP_NET_BIND_SERVICE)) {
> +			err = -EACCES;
> +			goto done;
> +		}
>  	}

Maybe there is actually a second place for adding that comment.

Otherwise I am fine with this, but since it is not a regression, this
will be only taking in the next tree.

Regards

Marcel



  reply	other threads:[~2010-08-10 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 19:00 [PATCH v4 0/5] L2CAP updates for FCS, valid PSMs, and stream recv Mat Martineau
2010-08-10 19:00 ` [PATCH 1/5] Bluetooth: Only enable L2CAP FCS for ERTM or streaming Mat Martineau
2010-08-10 21:17   ` Marcel Holtmann
2010-08-10 19:00 ` [PATCH 2/5] Bluetooth: Validate PSM values in calls to connect() and bind() Mat Martineau
2010-08-10 21:21   ` Marcel Holtmann [this message]
2010-08-10 19:00 ` [PATCH 3/5] Bluetooth: Add common code for stream-oriented recvmsg() Mat Martineau
2010-08-10 19:00 ` [PATCH 4/5] Bluetooth: Use common SOCK_STREAM receive code in RFCOMM Mat Martineau
2010-08-10 19:00 ` [PATCH 5/5] Bluetooth: Use a stream-oriented recvmsg with SOCK_STREAM L2CAP sockets Mat Martineau
  -- strict thread matches above, loose matches on Subject: below --
2010-08-24 22:35 [PATCH v5 0/5] L2CAP updates for FCS, valid PSMs, and stream recv Mat Martineau
2010-08-24 22:35 ` [PATCH 2/5] Bluetooth: Validate PSM values in calls to connect() and bind() Mat Martineau

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=1281475270.12579.223.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=gustavo@padovan.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mathewm@codeaurora.org \
    --cc=rshaffer@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).