linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: iulia-tanasescu <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] c0156e: gatt-server: Check pointer before memcpy
Date: Tue, 13 Jun 2023 14:31:00 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/d2d2d1-ddd095@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: c0156edd198eef10c847b3540098cb4b9d18d142
      https://github.com/bluez/bluez/commit/c0156edd198eef10c847b3540098cb4b9d18d142
  Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
  Date:   2023-06-13 (Tue, 13 Jun 2023)

  Changed paths:
    M src/shared/gatt-server.c

  Log Message:
  -----------
  gatt-server: Check pointer before memcpy

This adds a check before calling memcpy inside
bt_gatt_server_send_notification, to avoid getting
the following error in case the user wants to send
an empty notification for an attribute:

src/shared/gatt-server.c:1789:3: runtime error:
null pointer passed as argument 2, which is declared to never be null


  Commit: ddd09531e936508ba9ea620f9caaf3402c54496f
      https://github.com/bluez/bluez/commit/ddd09531e936508ba9ea620f9caaf3402c54496f
  Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
  Date:   2023-06-13 (Tue, 13 Jun 2023)

  Changed paths:
    M src/shared/bass.c

  Log Message:
  -----------
  shared/bass: Implement CP opcode handlers

This adds handlers for the following BASS Broadcast Audio Scan
Control Point opcodes:
   Remote Scan Stopped
   Remote Scan Started
   Remove Source


Compare: https://github.com/bluez/bluez/compare/d2d2d12f59d6...ddd09531e936

                 reply	other threads:[~2023-06-13 21:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bluez/bluez/push/refs/heads/master/d2d2d1-ddd095@github.com \
    --to=noreply@github.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;
as well as URLs for NNTP newsgroup(s).