From: Pauli Virtanen <pav@iki.fi>
To: Bharath SM <bharathsm.hsk@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Bharath SM <bharathsm@microsoft.com>
Subject: Re: [PATCH] Bluetooth: Fix unused value warning in sco_sock_connect
Date: Sat, 23 Mar 2024 11:51:36 +0200 [thread overview]
Message-ID: <84700000098a32b0a1375ffde5a1a852072b93fd.camel@iki.fi> (raw)
In-Reply-To: <20240323072253.40816-1-bharathsm@microsoft.com>
Hi,
la, 2024-03-23 kello 12:52 +0530, Bharath SM kirjoitti:
> Coverity complains of an unused value:
>
> CID 1528147: (#1 of 1): Unused value (UNUSED_VALUE)
> assigned_value: Assigning value -22 to err here, but that stored
> value is overwritten before it can be used.
> err = -EINVAL;
>
> Fix it by removing the assignment.
>
> Signed-off-by: Bharath SM <bharathsm@microsoft.com>
> ---
> net/bluetooth/sco.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/net/bluetooth/sco.c b/net/bluetooth/sco.c
> index 43daf965a01e..e74bce4e1d6c 100644
> --- a/net/bluetooth/sco.c
> +++ b/net/bluetooth/sco.c
> @@ -581,9 +581,6 @@ static int sco_sock_connect(struct socket *sock, struct sockaddr *addr, int alen
> if (sk->sk_state != BT_OPEN && sk->sk_state != BT_BOUND)
> return -EBADFD;
>
> - if (sk->sk_type != SOCK_SEQPACKET)
> - err = -EINVAL;
> -
It should return -EINVAL here, not remove the check.
Looks like it got broken in 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 in
the locking refactoring.
> lock_sock(sk);
> /* Set destination address and psm */
> bacpy(&sco_pi(sk)->dst, &sa->sco_bdaddr);
--
Pauli Virtanen
prev parent reply other threads:[~2024-03-23 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 7:22 [PATCH] Bluetooth: Fix unused value warning in sco_sock_connect Bharath SM
2024-03-23 7:57 ` bluez.test.bot
2024-03-23 9:51 ` Pauli Virtanen [this message]
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=84700000098a32b0a1375ffde5a1a852072b93fd.camel@iki.fi \
--to=pav@iki.fi \
--cc=bharathsm.hsk@gmail.com \
--cc=bharathsm@microsoft.com \
--cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox