From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-21.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT, USER_IN_DEF_DKIM_WL autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0F29DC433ED for ; Mon, 5 Apr 2021 23:33:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D750461026 for ; Mon, 5 Apr 2021 23:33:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241750AbhDEXdf (ORCPT ); Mon, 5 Apr 2021 19:33:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45952 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237964AbhDEXdc (ORCPT ); Mon, 5 Apr 2021 19:33:32 -0400 Received: from mail-qt1-x84a.google.com (mail-qt1-x84a.google.com [IPv6:2607:f8b0:4864:20::84a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8250CC061788 for ; Mon, 5 Apr 2021 16:33:25 -0700 (PDT) Received: by mail-qt1-x84a.google.com with SMTP id d18so2151475qtn.16 for ; Mon, 05 Apr 2021 16:33:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:message-id:mime-version:subject:from:to:cc; bh=iix/v2cJC9b8/wrwd7EH/KvNJQF53WPoD5HVyQhNhJI=; b=PWuWgElMYtHYjSyuGEO6ucZsbDjGBg7VQEFwyAtX2nPGC8Vq0mnFEpGdifIavZomsW KtYUty/PgMrBszumWX5Pd9hQlLOcqfnC4nJ/k8VozzFM3wf46mfWNmPTIWz8RVbmz7j/ 0TIOT5d5MM+uLoK/sdcUVoK6bC99T8N66r9Gb80vAkxpLFpsa7eBWKTawWBNroI9dD3H ol/+q4GLB7tapCPX0l6i2ApVWfZ4sSLvDRba62WcQV05+Hc8/2NVGMSxl1BqzsB4aOKy JK3xNkaun8XA2gHy64xxqFfD2EhkIMLAcgv+S7TgLbhzHkvdSJEIKamhFa5bSiX9UGze 0VwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:mime-version:subject:from:to:cc; bh=iix/v2cJC9b8/wrwd7EH/KvNJQF53WPoD5HVyQhNhJI=; b=FxbLEWQjlBsc41G764a/c/o3OCXIEccdWVF3/MmCz3iR+8wRDZiYXoXm7AhqJqAhxS SDtpu44eqZ5Z2GQGUIRf3eqLC5bgeyHXJ8RgryU44U/l+lUi1ZcryGsZQ4TEPGvEKHfJ d0Gg0ijri54JCdTroqxRXEeNAJl4paVPYKFrROtV8VaImUc2UF2TKN8iCUppY4+ZvHOx fuldFfH/ZBeNj3KTivELV4zzpz8jQVMTsjgY20goWIM9aZEFyqGqmDpBlkm62umcR9XU CpPaoHgGpYr/MwnbYTxY4QCQlVTo41RcqtF60jWSIHswIPTOc1xOjYODmVy/AQ/Lskra 8KKw== X-Gm-Message-State: AOAM532luJfL9EDr7j8G3jwp58xdhbCah6GcTJ/yYgnJ12vxckEwThrb azU/MIIiOmR8g6ul5S+kpXgYBGTqillkqOE/CVP6 X-Google-Smtp-Source: ABdhPJypo2nkY7qRmSPpYGVr8CAc+F+j4KKJ9X64kRJ8m77Hhve8ftYeL3Ovp7Ik4xyLMd3LH/sq+B9C27XwwHPyBDD+ X-Received: from danielwinkler-linux.mtv.corp.google.com ([2620:15c:202:201:1cb3:ad22:2ed6:7c62]) (user=danielwinkler job=sendgmr) by 2002:ad4:5593:: with SMTP id e19mr14604643qvx.52.1617665604297; Mon, 05 Apr 2021 16:33:24 -0700 (PDT) Date: Mon, 5 Apr 2021 16:33:03 -0700 Message-Id: <20210405233305.92431-1-danielwinkler@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.31.0.208.g409f899ff0-goog Subject: [PATCH 0/2] Bluetooth: Avoid centralized adv handle tracking for extended features From: Daniel Winkler To: marcel@holtmann.org, linux-bluetooth@vger.kernel.org Cc: chromeos-bluetooth-upstreaming@chromium.org, Daniel Winkler , "David S. Miller" , Jakub Kicinski , Johan Hedberg , Luiz Augusto von Dentz , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Maintainers, This series addresses a race condition where an advertisement registration can conflict with a software rotation advertisement refresh. I found that this issue was only occurring with the new extended MGMT advertising interface. A bad use of the hdev->cur_adv_instance caused every new instance to be immediately sent to the controller rather than queued for software rotation, opening a path for the race to occur. This series improves the way new extended advertising hci callbacks track the relevant adv handle, removing the need for the cur_adv_instance use. In a separate patch, the incorrect usage of cur_adv_instance is removed, to align the extended MGMT commands to the original add_advertising usage. The series was tested on both extended and non-extended bluetooth controllers to confirm that the race condition is resolved, and that multi- and single-advertising automated test scenarios are still successful. Thanks in advance, Daniel Daniel Winkler (2): Bluetooth: Use ext adv handle from requests in CCs Bluetooth: Do not set cur_adv_instance in adv param MGMT request net/bluetooth/hci_event.c | 16 +++++++--------- net/bluetooth/mgmt.c | 1 - 2 files changed, 7 insertions(+), 10 deletions(-) -- 2.31.0.208.g409f899ff0-goog