All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] unit/test-gatt: Fix hung issue
Date: Fri, 24 Aug 2018 13:28:58 +0800	[thread overview]
Message-ID: <5B7F979A.1060806@windriver.com> (raw)
In-Reply-To: <20180824053001.102917-1-mingli.yu@windriver.com>

Please ignore this.

Thanks,


On 2018年08月24日 13:30, mingli.yu@windriver.com wrote:
> From: Brian Gix <brian.gix@intel.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,
>

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

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

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=5B7F979A.1060806@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.