archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <>
To: Dan Carpenter <>
Cc: "Frédéric Dalleau" <>,
	"Johan Hedberg" <>,
	"Luiz Augusto von Dentz" <>,
	"Gustavo Padovan" <>,,
Subject: Re: [PATCH] Bluetooth: sco: prevent information leak in sco_conn_defer_accept()
Date: Thu, 22 Jul 2021 16:14:09 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <YNXveZZwzS3crmHH@mwanda>

Hi Dan,

> Smatch complains that some of these struct members are not initialized
> leading to a stack information disclosure:
>    net/bluetooth/sco.c:778 sco_conn_defer_accept() warn:
>    check that 'cp.retrans_effort' doesn't leak information
> This seems like a valid warning.  I've added a default case to fix
> this issue.  It's sort of unusual to have case SCO_AIRMODE_CVSD,
> followed by a default case but I think it's nicely readable.  :)
> Fixes: 2f69a82acf6f ("Bluetooth: Use voice setting in deferred SCO connection request")
> Signed-off-by: Dan Carpenter <>
> ---
> net/bluetooth/sco.c | 1 +
> 1 file changed, 1 insertion(+)

I actually prefer a separate default statement since otherwise I get confused. Your patch with that minor change has been applied to bluetooth-next tree.



      parent reply	other threads:[~2021-07-22 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 15:00 [PATCH] Bluetooth: sco: prevent information leak in sco_conn_defer_accept() Dan Carpenter
2021-06-25 16:17 `
2021-06-25 19:59   ` Dan Carpenter
2021-06-25 20:33     ` Luiz Augusto von Dentz
2021-07-08  7:11 `
2021-07-22 14:14 ` Marcel Holtmann [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).