linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <mingli.yu@windriver.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: [PATCH] unit/test-gatt: Fix hung issue
Date: Thu, 23 Aug 2018 22:33:31 -0700	[thread overview]
Message-ID: <20180824053331.103927-1-mingli.yu@windriver.com> (raw)

From: Mingli Yu <mingli.yu@windriver.com>

The below test hangs infinitely
$ unit/test-gatt -p  /robustness/unkown-request -d
/robustness/unkown-request - init
/robustness/unkown-request - setup
/robustness/unkown-request - setup complete
/robustness/unkown-request - run
  GATT: < 02 17 00                                         ...
  bt_gatt_server:MTU exchange complete, with MTU: 23
  GATT: > 03 00 02                                         ...
  PDU: = 03 00 02                                         ...
  GATT: < bf 00

Actually, the /robustness/unkown-request test does
no action.
---
 unit/test-gatt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/unit/test-gatt.c b/unit/test-gatt.c
index c7e28f865..b57373b07 100644
--- a/unit/test-gatt.c
+++ b/unit/test-gatt.c
@@ -4463,7 +4463,7 @@ int main(int argc, char *argv[])
 			test_server, service_db_1, NULL,
 			raw_pdu(0x03, 0x00, 0x02),
 			raw_pdu(0xbf, 0x00),
-			raw_pdu(0x01, 0xbf, 0x00, 0x00, 0x06));
+			raw_pdu());
 
 	define_test_server("/robustness/unkown-command",
 			test_server, service_db_1, NULL,
-- 
2.17.1

             reply	other threads:[~2018-08-24  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  5:33 mingli.yu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-24  5:30 [PATCH] unit/test-gatt: Fix hung issue mingli.yu
2018-08-24  5:28 ` Yu, Mingli
2018-08-24  6:02   ` Yu, Mingli
2018-08-24  7:42     ` Luiz Augusto von Dentz

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=20180824053331.103927-1-mingli.yu@windriver.com \
    --to=mingli.yu@windriver.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).