public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: 이주영 <tkakel@naver.com>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] I've found a bug in sdp_cstate_get() function.
Date: Thu, 20 Mar 2008 01:03:21 +0900	[thread overview]
Message-ID: <1e720e88bd7ce5a74be321703f24060d@i61813> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 457 bytes --]

Hi,
 
I've found a bug in sdp_cstate_get() function.
(bluez-utils/dist/sdpd/request.c)
 -> memcpy(cstate, (sdp_cont_state_t *)pdata, sizeof(sdp_cont_state_t));
When running this code, "hcid daemon crash" occurred.(memory alignment error)
I think there's a bug with (sdp_cont_state_t *)pdata in sdp_cstate_get() function.
I fixed this code.
 -> memcpy(cstate, pdata, sizeof(sdp_cont_state_t));
Now, hcid daemon doesn't die.
 
 
tkakel님의 블로그
안녕하세요.

[-- Attachment #1.2: Type: text/html, Size: 2739 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-03-19 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 16:03 이주영 [this message]
2008-03-19 16:47 ` [Bluez-devel] I've found a bug in sdp_cstate_get() function Marcel Holtmann
2008-03-20  4:01   ` 이주영
2008-03-20 12:43     ` Marcel Holtmann
2008-03-20 11:22   ` [Bluez-devel] RFCOMM sockets Fabrizio Guglielmino
2008-03-20 12:45     ` 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=1e720e88bd7ce5a74be321703f24060d@i61813 \
    --to=tkakel@naver.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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