Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp135794ybm; Wed, 22 May 2019 00:10:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqwPGcfBnLYiPA96Y/kEnQzD3yOI0tcci0nc+wt0cXrnm5sGwVhT+mEzWys6lGqAd3F3XWHn X-Received: by 2002:a17:902:3283:: with SMTP id z3mr62250731plb.278.1558509040153; Wed, 22 May 2019 00:10:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558509040; cv=none; d=google.com; s=arc-20160816; b=w07dLEtHsP+x/Fgph7GLQISCnd4PtJZQXOs5+z7ho7OQ3CMgQUnVRqWBDJVVx+bcbo CPxqCisOdfFzU4DfioCYho97u+w+zBEcPwBFjn+hIFHZsc2frGWRbxfxGAkVL9BQFNFH f8Z8mzLi2P56zGQVIK2D4OCdccKkwiseSNev9eXKuGUD340ThgJKoa1NQ8GbutU7YU+N p3HeDNB8wMBDVAg+SV6IcbS5+Se9/rUSQ6QG3VahnI7CDL8Cr6BexH9CPqtZNJPZip62 XgMZv3Ooa26UcwYU4atdWEKoPyvHOP+MoXaYZ2bG25Wbl8gM0BmSUImpCKdtcDYlzKpF PdZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=GSUe+8dphbSQABUldVZmHCAY73l389XuBJdE0F0myO4=; b=h2ZoWXq+HRzsn5CeGX/d3G7tD+W7q0S6jV4rFGCydGiplzE5Nb3a0z3u4TxJ/vQ30X t3iNHC0lOKqtsucQzcll8wClK5uPP3J4RQZSZVpFo+Fbv5xmSMyPFTUHkYfLlXz45l4V OLE5Zz/4XviBj506iGn8GzpIIu728/tOhfYEo9O59TwYMO+3XLN5wTq9FXFdueJvRVul FbM7ifwxfHcH/xhBbVe6/HbrNyxEHT7wGy9vDcZoWpover2V73QrWovRWwfvTclBtuWb KMYriOzLaCK/pKKI2k9vp+iUeLn+3rvIo8QySf6SCHW01JH5Uf+44rF4SD6/KT2jRrWN 8UKA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h7si25419726plk.203.2019.05.22.00.10.24; Wed, 22 May 2019 00:10:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728536AbfEVHIF convert rfc822-to-8bit (ORCPT + 99 others); Wed, 22 May 2019 03:08:05 -0400 Received: from coyote.holtmann.net ([212.227.132.17]:55670 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727453AbfEVHIE (ORCPT ); Wed, 22 May 2019 03:08:04 -0400 Received: from marcel-macpro.fritz.box (p5B3D2A37.dip0.t-ipconnect.de [91.61.42.55]) by mail.holtmann.org (Postfix) with ESMTPSA id 0887ACF183; Wed, 22 May 2019 09:16:22 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [PATCH] Revert "Bluetooth: Align minimum encryption key size for LE and BR/EDR connections" From: Marcel Holtmann In-Reply-To: <6BD1D3F7-E2F2-4B2D-9479-06E27049133C@holtmann.org> Date: Wed, 22 May 2019 09:08:02 +0200 Cc: Johan Hedberg , "David S. Miller" , linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: <7B7F362B-6C8B-4112-8772-FB6BC708ABF5@holtmann.org> References: <20190522052002.10411-1-anarsoul@gmail.com> <6BD1D3F7-E2F2-4B2D-9479-06E27049133C@holtmann.org> To: Vasily Khoruzhick X-Mailer: Apple Mail (2.3445.104.11) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vasily, >> This reverts commit d5bb334a8e171b262e48f378bd2096c0ea458265. >> >> This commit breaks some HID devices, see [1] for details >> >> https://bugzilla.kernel.org/show_bug.cgi?id=203643 >> >> Signed-off-by: Vasily Khoruzhick >> Cc: stable@vger.kernel.org > > let me have a look at this. Maybe there is a missing initialization for older HID devices that we need to handle. Do you happen to have the full btmon binary trace from controller initialization to connection attempt for me? > > Are both devices Bluetooth 2.1 or later device that are supporting Secure Simple Pairing? Or is one of them a Bluetooth 2.0 or earlier device? I am almost certain that you have a Bluetooth 2.0 mouse. I made a really stupid mistake in the key size check logic and forgot to bind it to SSP support. Can you please check the patch that I just send you. https://lore.kernel.org/linux-bluetooth/20190522070540.48895-1-marcel@holtmann.org/T/#u Regards Marcel